[Kernel-packages] [Bug 1650895] Re: Several new Asus laptops are missing touchpad support
" It was later fixed in the kernel with commit c8b1b3dd89ea7b3f77a73e59c4c4495e16338e15." I'm unable to use git at the moment but I remember seeing commit with description that it fixes keyboard support. And if I've seen it, I've compiled and tested it for sure. I broke WiFi of my E502SA with disconnecting battery: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653361/comments/13 And haven't used the computer much since, but looking at that comment, last kernel I've tested was 4.10.0rc5 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650895 Title: Several new Asus laptops are missing touchpad support Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: E502SA and several other new Asus laptops are missing touchpad support. Support for the Asus touchpad has been introduced only recently: http://www.spinics.net/lists/linux-input/msg48143.html From the development kernel git: "commit 9ce12d8be12c94334634dd57050444910415e45f Author: Brendan McGrath Date: Tue Nov 29 18:59:25 2016 +1100 HID: asus: Add i2c touchpad support Update the hid-asus module to add multitouch support for the Asus i2c touchpad. This patch aims to resolve the issue raised here:E https://bugzilla.kernel.org/show_bug. The latest mainline kernel, Linux 4.9 that was released 11th of December doesn't contain this patch. I was able to get touchpad features to work with E502SA after patching Xenial Xerus kernel with the above patch and the patches it depends on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamse 2045 F pulseaudio CurrentDesktop: Unity Date: Sun Dec 18 15:41:30 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d46d5e40-bd0f-41a5-87bb-f4f470f7b4d6 InstallationDate: Installed on 2016-12-14 (4 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 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E502SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed root=UUID=17457b58-fc63-470b-a916-2eedb0dbd58e ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-53-generic N/A linux-backports-modules-4.4.0-53-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E502SA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E502SA 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.:bvrE502SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE502SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE502SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E502SA 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/1650895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@Nils, With the current default value, your NVMe will transit to PS4. So let's add kernel parameter 'nvme-core.nvme_core.default_ps_max_latency_us=2000' to test if PS3 also shares the same issue. If this issue persists, use 'nvme-core.nvme_core.default_ps_max_latency_us=0' to turn APST off. @Ben, Is your laptop XPS 9550/Precision 5510, too? Please try 'nvme-core.nvme_core.default_ps_max_latency_us=5500', if the issue persists, please try 'nvme- core.nvme_core.default_ps_max_latency_us=200'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@Ben, I saw that you uses XPS 9550, the comment was clipped at the bottom. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683509] Re: WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0()
Unable to run apport-collect. ** 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/1683509 Title: WARNING: CPU: 0 PID: 1 at /build/linux- 1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Status in linux package in Ubuntu: Confirmed Bug description: [ cut here ] WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Modules linked in: autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ixgbe dca vxlan ip6_udp_tunnel udp_tunnel raid1 ahci ptp hpsa pps_core psmouse libahci scsi_transport_sas mdio wmi fjes CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-64-generic #85-Ubuntu 0286 15383995 880ff8feb900 813f8083 81cd1748 880ff8feb938 810812d2 88103fffd6c0 0034 024040c0 Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] __alloc_pages_slowpath.constprop.88+0x9ed/0xad0 [] ? get_page_from_freelist+0xcb/0xa50 [] ? console_unlock+0x1d5/0x550 [] __alloc_pages_nodemask+0x286/0x2a0 [] ? vprintk_emit+0x2d7/0x520 [] alloc_pages_current+0x8c/0x110 [] alloc_kmem_pages+0x19/0x90 [] kmalloc_order_trace+0x2e/0xe0 [] __kmalloc+0x22e/0x250 [] erst_reader+0x151/0x470 [] ? d_rehash+0x4c/0x60 [] pstore_get_records+0xbc/0x3e0 [] ? parse_options+0x90/0x90 [] pstore_fill_super+0xa9/0xc0 [] mount_single+0x8b/0xb0 [] pstore_mount+0x18/0x20 [] mount_fs+0x38/0x160 [] ? __alloc_percpu+0x15/0x20 [] vfs_kern_mount+0x67/0x110 [] do_mount+0x25f/0xda0 [] ? __kmalloc_track_caller+0x1b4/0x250 [] ? memdup_user+0x42/0x70 [] SyS_mount+0x9f/0x100 [] entry_SYSCALL_64_fastpath+0x16/0x71 ---[ end trace fa5b6f4ddc4df171 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683510] Re: WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0()
Unable to run apport-collect. ** 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/1683510 Title: WARNING: CPU: 0 PID: 0 at /build/linux- 1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Status in linux package in Ubuntu: Confirmed Bug description: [ cut here ] WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-64-generic #85-Ubuntu 0086 394369744a471514 81e03e10 813f8083 81ca9210 81e03e48 810812d2 0020 81e03ec8 0001 002b Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] mach_get_cmos_time+0x186/0x1a0 [] read_persistent_clock+0xf/0x20 [] read_persistent_clock64+0x29/0x60 [] ? _set_gate.isra.2.constprop.5+0x74/0x91 [] timekeeping_init+0x23/0x1c4 [] ? _cond_resched+0x5/0x30 [] ? _cond_resched+0x5/0x30 [] ? mutex_lock+0x12/0x30 [] ? find_next_bit+0x15/0x20 [] start_kernel+0x2d4/0x4a2 [] ? early_idt_handler_array+0x120/0x120 [] x86_64_start_reservations+0x2a/0x2c [] x86_64_start_kernel+0x14a/0x16d ---[ end trace 73a280b8d116bceb ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1643455] Re: Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10
Please try version >= v4.11-rc2, it has two more seems related commits: 5ffa572a431ff3fd6175419656603519fa471c27 platform/x86: acer-wmi: add another KEY_WLAN keycode 280642c3c8dda79da39e056fd5480d1c3942524e platform/x86: acer-wmi: Inform firmware that RF Button Driver is active -- 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/1643455 Title: Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On an Acer V3-574-7481 with built-in stock Intel 7265 wireless hardware, WiFi works perfectly but Bluetooth does not. The System Settings applet reports "No Bluetooth adapters found" and the option to enable Bluetooth is grayed out. However, Bluetooth hardware is reported by "dmesg" and a firmware patch file is applied automatically during boot. *Bluetooth works on this same machine booted into Windows 10.* The machine is dual-boot from separate partitions. # uname -a Linux galois-l 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # head -6 /etc/os-release NAME="Ubuntu" VERSION="16.10 (Yakkety Yak)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.10" VERSION_ID="16.10" # rfkill list 1: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no # lspci -knn | grep -A3 Net 03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi # lsusb Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 003: ID 04f2:b526 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # hcitool dev Devices: # hcitool scan Device is not available: No such device # dmesg | grep -i bluetooth [ 26.310459] Bluetooth: Core ver 2.21 [ 26.310476] Bluetooth: HCI device and connection manager initialized [ 26.310478] Bluetooth: HCI socket layer initialized [ 26.310480] Bluetooth: L2CAP socket layer initialized [ 26.310483] Bluetooth: SCO socket layer initialized [ 26.514833] Bluetooth: hci0: read Intel version: 370810011003110e00 [ 26.794565] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq [ 26.987853] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 39.604402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 39.604404] Bluetooth: BNEP filters: protocol multicast [ 39.604407] Bluetooth: BNEP socket layer initialized # locate ibt-hw /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq /lib/firmware/intel/ibt-hw-37.7.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq /lib/firmware/intel/ibt-hw-37.8.bseq # dpkg -S /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq linux-firmware: /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq # dpkg -s linux-firmware | grep Version Version: 1.161 This behavior was identical first under Ubuntu 16.04 and then under 16.10 after upgrade. Command and response examples above are under 16.10 after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1643455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I'm also experiencing issues since ugprading to 17.04. When I switch to another TTY (via ctrl-alt-f1) the following errors get printed to the screen: [ 746.341551] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #525023: comm NetworkManager: reading directory iblock 0 [ 746.343318] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #524289: comm pool: reading directory iblock 0 [ 746.356125] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272213: comm systemd-udevd: reading directory iblock 0 [ 746.356139] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272210: comm systemd-udevd: reading directory iblock 0 [ 746.356332] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272193: comm systemd-udevd: reading directory iblock 0 [ 746.356338] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272825: comm systemd-udevd: reading directory iblock 0 [ 746.356400] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272210: comm systemd-udevd: reading directory iblock 0 [ 746.474632] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #524539: comm unity-settings-: reading directory iblock 0 [ 746.992814] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #5506108: comm BrowserBlocking: reading directory iblock 0 [ 746.304451] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #5506117: comm BrowserBlocking: reading directory iblock 0 I also tried to run `smartctl -t long /dev/nvme0n1p7` however the results seem to indicate that the tool doesn't work with my particular SSD: smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.0-19-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: PM951 NVMe SAMSUNG 512GB Serial Number: S29PNX0H611013 Firmware Version: BXV77D0Q PCI Vendor/Subsystem ID:0x144d IEEE OUI Identifier:0x002538 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization:254,982,533,120 [254 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Mon Apr 17 17:45:48 2017 AEST Firmware Updates (0x06):3 Slots Optional Admin Commands (0x0017): Security Format Frmw_DL *Other* Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 6.00W --0 0 0 05 5 1 + 4.20W --1 1 1 1 30 30 2 + 3.10W --2 2 2 2 100 100 3 - 0.0700W --3 3 3 3 5005000 4 - 0.0050W --4 4 4 4 2000 22000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === Read NVMe SMART/Health Information failed: NVMe Status 0x2002 - I'm using a Dell XPS 15 9550. Is there anything I can do to help you guys debug the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
No, it's a Lenovo ThinkPad X270. Do you need any other 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/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces
** Tags removed: severity-critical ** Tags added: severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1664545 Title: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces Status in makedumpfile package in Ubuntu: New Bug description: In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on guest while kdump process console got hung having call traces Reproducible Step: 1- Install Ubuntu17.04 as kvm guest on ubuntu kvm host 2- configure kdump 3- trigger kdump Expected Result : Kdump should capture Actual Result : Kdump console hung having continuous call traces LOG: [0.488534] Freeing unused kernel memory: 4416K (c8e8 - c92d) [0.488725] This architecture does not have kernel memory protection. Loading, please wait... starting version 232 [0.501616] random: udevadm: uninitialized urandom read (16 bytes read) [0.501830] random: udevadm: uninitialized urandom read (16 bytes read) [0.501981] random: udevadm: uninitialized urandom read (16 bytes read) [0.502162] random: udevadm: uninitialized urandom read (16 bytes read) [0.502254] random: udevadm: uninitialized urandom read (16 bytes read) [0.502433] random: udevadm: uninitialized urandom read (16 bytes read) [0.503188] random: udevadm: uninitialized urandom read (16 bytes read) [0.503270] random: udevadm: uninitialized urandom read (16 bytes read) [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes read) [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds. [ 242.663514] Not tainted 4.9.0-15-generic #16-Ubuntu [ 242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663755] systemd-udevd D0 151145 0x00040002 [ 242.663795] Call Trace: [ 242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0 [ 242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990 [ 242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0 [ 242.664179] [c0001fe4ee40] [c8b1de54] schedule_timeout+0x274/0x470 [ 242.664334] [c0001fe4ef30] [c8b19010] io_schedule_timeout+0xd0/0x160 [ 242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90 [ 242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170 [ 242.664754] [c0001fe4f000] [c824b238] wait_on_page_bit+0x98/0xb0 [ 242.664847] [c0001fe4f060] [c824d60c] do_read_cache_page+0x21c/0x4e0 [ 242.665008] [c0001fe4f0d0] [c859be78] read_dev_sector+0xb8/0x140 [ 242.665126] [c0001fe4f100] [c85a5d88] read_lba.isra.0+0x148/0x250 [ 242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830 [ 242.665363] [c0001fe4f2e0] [c859e768] check_partition+0x158/0x2d0 [ 242.665469] [c0001fe4f360] [c859c760] rescan_partitions+0xe0/0x390 [ 242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490 [ 242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0 [ 242.665784] [c0001fe4f550] [c8599538] device_add_disk+0x4a8/0x500 [ 242.665894] [c0001fe4f600] [d0511cc8] virtblk_probe+0x560/0x928 [virtio_blk] [ 242.665983] [c0001fe4f6c0] [c8687700] virtio_dev_probe+0x1d0/0x350 [ 242.666050] [c0001fe4f700] [c8716f30] driver_probe_device+0x240/0x540 [ 242.666116] [c0001fe4f790] [c871738c] __driver_attach+0x15c/0x160 [ 242.666174] [c0001fe4f810] [c87138ec] bus_for_each_dev+0x8c/0xf0 [ 242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50 [ 242.666289] [c0001fe4f880] [c8715a78] bus_add_driver+0x238/0x380 [ 242.666345] [c0001fe4f910] [c871829c] driver_register+0x9c/0x180 [ 242.666403] [c0001fe4f980] [c8686abc] register_virtio_driver+0x4c/0x60 [ 242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 [virtio_blk] [ 242.666527] [c0001fe4fa10] [c800dde8] do_one_initcall+0x68/0x1d0 [ 242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244 [ 242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0 [ 242.666701] [c0001fe4fd30] [c8184c60] SyS_finit_module+0xf0/0x170 [ 242.666759] [c0001fe4fe30] [c800bd84] system_call+0x38/0xe0 [ 363.701100] md: raid6 pe
[Kernel-packages] [Bug 1683587] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1683587 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Incomplete Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. The kernel patch to support these new devices is: https://github.com/torvalds/linux/commit/45f4f2eb3da3cbff02c3d77c784c81320c733056 The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Trusty onwards. The upstream commit is going in for 4.11, so this will need to be backported to v3.13/v4.4/v4.8/v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683587] [NEW] LSI Harpoon support in megaraid_sas module
Public bug reported: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. The kernel patch to support these new devices is: https://github.com/torvalds/linux/commit/45f4f2eb3da3cbff02c3d77c784c81320c733056 The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Trusty onwards. The upstream commit is going in for 4.11, so this will need to be backported to v3.13/v4.4/v4.8/v4.10. I am working on SRU patches for this. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: 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/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Incomplete Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. The kernel patch to support these new devices is: https://github.com/torvalds/linux/commit/45f4f2eb3da3cbff02c3d77c784c81320c733056 The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Trusty onwards. The upstream commit is going in for 4.11, so this will need to be backported to v3.13/v4.4/v4.8/v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663727] Re: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors
[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/1663727 Title: 16.04.2 LTS (4.4.0-62-generic) now spewing EDID vga radeon errors Status in linux package in Ubuntu: Expired Bug description: I've just performed an "apt-get update" on a Dell 2950 Server - which was already running 16.04.1 and now it's spewing EDID errors - I'm not sure what changed from 16.04.1 to 16.04.2.. I've attached dmesg to this, but basically it's dumping the following in logs and to the screen. [drm:radeon_vga_detect [radeon]] *ERROR* VGA-1: probed a monitor but no|invalid EDID --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 10 13:51 seq crw-rw 1 root audio 116, 33 Feb 10 13:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=97c6470f-0ecf-4fda-8400-9dcded48500c InstallationDate: Installed on 2014-04-18 (1034 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. PowerEdge 2950 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=089f7527-5b99-4ebc-9092-cd4461eebeb9 ro 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.8 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (206 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/30/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.0 dmi.board.name: 0H603H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.0:bd10/30/2010:svnDellInc.:pnPowerEdge2950:pvr:rvnDellInc.:rn0H603H:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge 2950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665182] Re: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
[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/1665182 Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Expired Bug description: I had been cleaning out old kernel images because my /boot/ directory was full and I couldn't install updates. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 2387 F pulseaudio /dev/snd/controlC0: user 2387 F pulseaudio Date: Wed Feb 15 10:37:33 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-02-20 (361 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Inspiron 7547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2016-10-04 (134 days ago) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0AM670 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/15/2015:svnDellInc.:pnInspiron7547:pvrNotSpecified:rvnDellInc.:rn0AM670:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7547 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@Nils, Is your laptop XPS 9550/Precision 5510, too? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] Re: multitouch gestures support is broken
This worked fine for me from a live 17.04 usb, but not on a system upgraded from 16.10. (Because of this, it seems unlikely that using an upstream kernel will make any difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I'm having the exact same problem (drive dying with filesystem read errors and system becoming unusable after using it for a while) However, my nvme SSD is not from Samsung, but from Toshiba: nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA 1 256.06 GB / 256.06 GB512 B + 0 B 51025KLA nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x1179 ssvid : 0x1179 sn : 177S10WYTAMT mn : THNSF5256GPUK TOSHIBA fr : 51025KLA rab : 1 ieee: 00080d cmic: 0 mdts: 0 cntlid : 0 ver : 0 rtd3r : 0 rtd3e : 0 oaes: 0 oacs: 0x17 acl : 3 aerl: 3 frmw: 0x2 lpa : 0x2 elpe: 127 npss: 5 avscc : 0 apsta : 0x1 wctemp : 351 cctemp : 355 mtfa: 0 hmpre : 0 hmmin : 0 tnvmcap : 0 unvmcap : 0 rpmbs : 0 sqes: 0x66 cqes: 0x44 nn : 1 oncs: 0x1e fuses : 0 fna : 0x4 vwc : 0x1 awun: 255 awupf : 0 nvscc : 0 acwu: 0 sgls: 0 subnqn : ps0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps1 : mp:3.90W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps2 : mp:2.00W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps3 : mp:0.1200W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps4 : mp:0.0120W non-operational enlat:5000 exlat:1 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- ps5 : mp:0.0060W non-operational enlat:10 exlat:5 rrt:5 rrl:5 rwt:5 rwl:5 idle_power:- active_power:- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubs
[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
@DevenPhillips: I'm a fellow bug sufferer, rather than Ubuntu maintainer, but if you're experiencing the same bug as myself then I've found I reliable workaround. Setting the `i8042.kbdreset=1` parameter to the kernel on boot seems to result in consistent detection of the touchpad. The easiest way to do that for me was to edit the /etc/default/grub file with the following line: GRUB_CMDLINE_LINUX_DEFAULT="i8042.kbdreset=1" and then running `sudo update-grub`. For me, this workaround was free of side-effects. In my situation the touchpad would either be detected (and work fine), or not be detected *at all*. I don't recall it being detected as the wrong device. As such, I've no idea if my workaround would be effective in your situation. Good luck! ~ Paul -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594214 Title: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop) Status in linux package in Ubuntu: Confirmed Bug description: On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is inconsistently detected at boot. Trying mainline 4.6 kernel did not help. WORKAROUND: Add kernel boot parameter: i8042.kbdreset=1 The device is id=17 on xinput below: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Kingsis Peripherals Evoluent VerticalMouse 3 id=12 [slave pointer (2)] ⎜ ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=14 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Power Buttonid=10 [slave keyboard (3)] ↳ Sleep Buttonid=11 [slave keyboard (3)] ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=13 [slave keyboard (3)] ↳ Chicony USB 2.0 Camera id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Jun 20 10:56:33 2016 InstallationDate: Installed on 2014-05-20 (761 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682826] Re: package linux-image-4.10.0-19-generic (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1
** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1682826 Title: package linux-image-4.10.0-19-generic (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Incomplete Bug description: applicazione package_hook si è chiusa inaspettatamente ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: franco 1668 F pulseaudio Date: Fri Apr 14 12:10:14 2017 ErrorMessage: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1 HibernationDevice: RESUME=UUID=d3610d43-b5ee-4802-9e06-32dfd1ff02ae MachineType: FUJITSU SIEMENS Amilo M1425 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=1eab16de-2aa9-4775-96ab-65c3d483067a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-19-generic (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) dmi.bios.date: 12/29/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080010 dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080010:bd12/29/2004:svnFUJITSUSIEMENS:pnAmiloM1425:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Amilo M1425 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682916] Re: WARNING: CPU: 3 PID: 429 at /build/linux-Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891 iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682916 Title: WARNING: CPU: 3 PID: 429 at /build/linux- Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891 iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi] Status in linux package in Ubuntu: Incomplete Bug description: [ 1371.109885] [ cut here ] [ 1371.109913] WARNING: CPU: 3 PID: 429 at /build/linux-Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891 iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi] [ 1371.109915] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080003d8) [ 1371.109917] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev samsung_laptop btusb btrtl intel_rapl btbcm btintel x86_pkg_temp_thermal intel_powerclamp bluetooth media coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel kvm snd_hda_codec irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usblp snd_hda_core cryptd snd_hwdep intel_cstate intel_rapl_perf input_leds joydev snd_pcm arc4 serio_raw snd_seq_midi [ 1371.109995] snd_seq_midi_event iwldvm mac80211 snd_rawmidi snd_seq iwlwifi lpc_ich snd_seq_device snd_timer cfg80211 snd shpchp mei_me mei soundcore dell_smo8800 mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci r8169 libahci mii wmi fjes video [ 1371.110055] CPU: 3 PID: 429 Comm: irq/29-iwlwifi Not tainted 4.10.0-19-generic #21-Ubuntu [ 1371.110057] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013 [ 1371.110059] Call Trace: [ 1371.110070] dump_stack+0x63/0x81 [ 1371.110075] __warn+0xcb/0xf0 [ 1371.110079] warn_slowpath_fmt+0x5f/0x80 [ 1371.110092] ? iwl_read32+0x1f/0x80 [iwlwifi] [ 1371.110107] iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi] [ 1371.110119] iwl_read_direct32+0x32/0x80 [iwlwifi] [ 1371.110132] iwl_dump_fh+0x268/0x390 [iwlwifi] [ 1371.110147] iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi] [ 1371.110160] iwl_pcie_irq_handler+0x3ae/0xa90 [iwlwifi] [ 1371.110167] ? irq_finalize_oneshot.part.35+0xf0/0xf0 [ 1371.110171] irq_thread_fn+0x20/0x50 [ 1371.110175] irq_thread+0x12f/0x1c0 [ 1371.110180] ? __schedule+0x23b/0x6f0 [ 1371.110185] ? irq_forced_thread_fn+0x70/0x70 [ 1371.110193] kthread+0x101/0x140 [ 1371.110197] ? irq_affinity_notify+0x130/0x130 [ 1371.110202] ? kthread_create_on_node+0x60/0x60 [ 1371.110208] ? SyS_exit_group+0x14/0x20 [ 1371.110213] ret_from_fork+0x2c/0x40 [ 1371.110218] ---[ end trace 5b7698dd06ffed08 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2009 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 14 16:54:41 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (628 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr
[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
I tried to run apport-collect but keep getting an error about unauthorized even after authorizing for Launchpad. Any other way I can get the system information to you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594214 Title: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop) Status in linux package in Ubuntu: Confirmed Bug description: On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is inconsistently detected at boot. Trying mainline 4.6 kernel did not help. WORKAROUND: Add kernel boot parameter: i8042.kbdreset=1 The device is id=17 on xinput below: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Kingsis Peripherals Evoluent VerticalMouse 3 id=12 [slave pointer (2)] ⎜ ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=14 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Power Buttonid=10 [slave keyboard (3)] ↳ Sleep Buttonid=11 [slave keyboard (3)] ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=13 [slave keyboard (3)] ↳ Chicony USB 2.0 Camera id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Jun 20 10:56:33 2016 InstallationDate: Installed on 2014-05-20 (761 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
This has been happening reliably on my Lenovo Y700 15ISK since 15.10... Sometimes it shows up as ETPS/2, sometimes PS/2, sometimes Logitech Wheelmouse... Most of the time it shows as "PS/2 Logitech Wheel Mouse" but none of the multitouch (2 finger scroll, 3 finger middle-click) can be set up. synclient says no device is present. ** Changed in: linux (Ubuntu) Status: Expired => 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/1594214 Title: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop) Status in linux package in Ubuntu: Confirmed Bug description: On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is inconsistently detected at boot. Trying mainline 4.6 kernel did not help. WORKAROUND: Add kernel boot parameter: i8042.kbdreset=1 The device is id=17 on xinput below: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Kingsis Peripherals Evoluent VerticalMouse 3 id=12 [slave pointer (2)] ⎜ ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=14 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Power Buttonid=10 [slave keyboard (3)] ↳ Sleep Buttonid=11 [slave keyboard (3)] ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=13 [slave keyboard (3)] ↳ Chicony USB 2.0 Camera id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Jun 20 10:56:33 2016 InstallationDate: Installed on 2014-05-20 (761 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
BTW, still happening on Zesty for that Lenovo... I will run a system report shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594214 Title: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop) Status in linux package in Ubuntu: Confirmed Bug description: On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is inconsistently detected at boot. Trying mainline 4.6 kernel did not help. WORKAROUND: Add kernel boot parameter: i8042.kbdreset=1 The device is id=17 on xinput below: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Kingsis Peripherals Evoluent VerticalMouse 3 id=12 [slave pointer (2)] ⎜ ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=14 [slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Power Buttonid=10 [slave keyboard (3)] ↳ Sleep Buttonid=11 [slave keyboard (3)] ↳ Sunrex/JME Ghost Key Elimiantion Keyboard id=13 [slave keyboard (3)] ↳ Chicony USB 2.0 Camera id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Jun 20 10:56:33 2016 InstallationDate: Installed on 2014-05-20 (761 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683165] Re: suspend/resume yields blank screen on NVIDIA desktop
> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Not as far as I know. Suspend/resume never worked on this platform. I tried several years ago and it did not work then, either. > Would it be possible for you to test the latest upstream kernel? Not easily I'm afraid, as I'd have to switch to the nouveau graphics driver, and as mentioned in Bug#1639180 Comment #65, on this platform nouveau crashes too often to be useful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683165 Title: suspend/resume yields blank screen on NVIDIA desktop Status in linux package in Ubuntu: Incomplete Bug description: On my desktop when I set "System settings > Power > Suspend when inactive for" to any time (5 minutes, say), and wait, Ubuntu suspends. When I power my desktop back on, it boots without the usual chatter on the screen and the screen stays entirely blank (the monitor is in power-save mode). At that point the only workaround is to force a reboot by holding down the power button for 4 seconds, and go through the ordinary boot process. This appears to be the same symptoms as Bug#1283938, the last comment of which says "file a bug by running 'ubuntu-bug linux'", which is what I've done here. I have had the problem for years but have not reported it until today. My desktop has an Asus M4N78 Pro motherboard, which uses an NVIDIA GeForce 8300 chipset. lspci reports the graphics controller as "NVIDIA Corporation C77 [GeForce 8300] (rev a2)". "Software & Updates" says I am using "NVIDIA legacy binary driver - version 304.135 from nvidia-304 (proprietary)". As discussed in Bug#1639180 comment#65, I cannot use the latest NVIDIA driver as it has so many artifacts on the screen that it is unusable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eggert 1825 F pulseaudio /dev/snd/controlC1: eggert 1825 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 16 09:38:00 2017 HibernationDevice: RESUME=UUID=433ca071-21cd-44b7-9b81-2b73c0463790 InstallationDate: Installed on 2014-04-27 (1084 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=0d7c67e2-db5b-493a-890b-90121ad2ee20 ro quiet splash acpi_enforce_resources=lax RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (358 days ago) dmi.bios.date: 07/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N78 PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682215] Re: [Hyper-V] mkfs regression in kernel 4.4+
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682215 Title: [Hyper-V] mkfs regression in kernel 4.4+ Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657539 This issue was fixed in Zesty, but also impacts the Xenial and Yakkety kernels. Can you please pull this patch back to Xenial+? https://git.kernel.org/cgit/linux/kernel/git/axboe/linux- block.git/commit/?h=for-4.11/block&id=729204ef49ec00b788ce23deb9eb922a5769f55d author Ming Lei 2016-12-17 10:49:09 (GMT) committer Jens Axboe 2017-01-12 03:47:08 (GMT) commit 729204ef49ec00b788ce23deb9eb922a5769f55d (patch) tree ab5cc3c0aa17fa8b988ed7dfefe888000fac0be3 parent 1661f2e21c8bbf922dcb76faf2126a33ffe4cddb (diff) block: relax check on sg gap If the last bvec of the 1st bio and the 1st bvec of the next bio are physically contigious, and the latter can be merged to last segment of the 1st bio, we should think they don't violate sg gap(or virt boundary) limit. Both Vitaly and Dexuan reported lots of unmergeable small bios are observed when running mkfs on Hyper-V virtual storage, and performance becomes quite low. This patch fixes that performance issue. The same issue should exist on NVMe, since it sets virt boundary too. Reported-by: Vitaly Kuznetsov Reported-by: Dexuan Cui Tested-by: Dexuan Cui Cc: Keith Busch Signed-off-by: Ming Lei Signed-off-by: Jens Axboe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682047] Re: linux-aws: 4.4.0-1015.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1682047 Title: linux-aws: 4.4.0-1015.24 -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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1682041 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682047/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682041] Re: linux: 4.4.0-74.95 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1682041 Title: linux: 4.4.0-74.95 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in 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 backports: 1682042 derivatives: 1682043,1682045,1682047,1682048 -- 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/1682041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683538] 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/1683538 Title: invalid opcode: [#1] SMP Status in linux package in Ubuntu: Confirmed Bug description: This is a relatively fresh installation of 17.04 on a relatively old Dell Optiplex. This message appears in /var/log/syslog: Apr 17 14:20:22 vancouver kernel: [ 3688.848621] [ cut here ] Apr 17 14:20:22 vancouver kernel: [ 3688.848628] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapo ps.h:129! Apr 17 14:20:22 vancouver kernel: [ 3688.848631] invalid opcode: [#1] SMP Apr 17 14:20:22 vancouver kernel: [ 3688.848633] Modules linked in: binfmt_misc dcdbas nvidia_uvm(POE) snd_hda_code c_hdmi coretemp kvm irqbypass serio_raw input_leds snd_usb_audio snd_hda_codec_analog snd_hda_codec_generic lpc_ich snd_hda_intel snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_raw midi snd_seq snd_seq_device snd_timer snd soundcore shpchp mac_hid parport_pc ppdev lp parport ip_tables x_tables a utofs4 hid_generic nvidia_drm(POE) nvidia_modeset(POE) psmouse nvidia(POE) usbhid pata_acpi hid tg3 drm_kms_helper ptp pps_core syscopyarea sysfillrect sysimgblt fb_sys_fops drm fjes Apr 17 14:20:22 vancouver kernel: [ 3688.848668] CPU: 0 PID: 2996 Comm: Socket Thread Tainted: P OE 4.1 0.0-19-generic #21-Ubuntu Apr 17 14:20:22 vancouver kernel: [ 3688.848670] Hardware name: Dell Inc. OptiPlex 745 /0TY565, BIOS 2.3.1 05/21/2007 Apr 17 14:20:22 vancouver kernel: [ 3688.848672] task: 89e76eac2a80 task.stack: 95ca0174 Apr 17 14:20:22 vancouver kernel: [ 3688.848679] RIP: 0010:__migration_entry_wait+0x16a/0x180 Apr 17 14:20:22 vancouver kernel: [ 3688.848681] RSP: :95ca01743d68 EFLAGS: 00010246 Apr 17 14:20:22 vancouver kernel: [ 3688.848683] RAX: 000fc0048078 RBX: bb21c4402bf0 RCX: bb21c4402bf0 Apr 17 14:20:22 vancouver kernel: [ 3688.848685] RDX: 0001 RSI: 89e6d00af148 RDI: bb21c27d0a40 Apr 17 14:20:22 vancouver kernel: [ 3688.848687] RBP: 95ca01743d80 R08: 89e76ad05540 R09: 89e76ad05540 Apr 17 14:20:22 vancouver kernel: [ 3688.848688] R10: R11: 0202 R12: bb21c27d0a40 Apr 17 14:20:22 vancouver kernel: [ 3688.848690] R13: 3e09f429 R14: 95ca01743e30 R15: 89e770e9fe10 Apr 17 14:20:22 vancouver kernel: [ 3688.848692] FS: 7f3559e21700() GS:89e77bc0() knlGS:00 00 Apr 17 14:20:22 vancouver kernel: [ 3688.848694] CS: 0010 DS: ES: CR0: 80050033 Apr 17 14:20:22 vancouver kernel: [ 3688.848696] CR2: 7f3506429000 CR3: 0001ad63e000 CR4: 06f0 Apr 17 14:20:22 vancouver kernel: [ 3688.848698] Call Trace: Apr 17 14:20:22 vancouver kernel: [ 3688.848702] migration_entry_wait+0x74/0x80 Apr 17 14:20:22 vancouver kernel: [ 3688.848706] do_swap_page+0x5b3/0x770 Apr 17 14:20:22 vancouver kernel: [ 3688.848709] ? futex_wake+0x90/0x170 Apr 17 14:20:22 vancouver kernel: [ 3688.848711] handle_mm_fault+0x873/0x1360 Apr 17 14:20:22 vancouver kernel: [ 3688.848715] __do_page_fault+0x23e/0x4e0 Apr 17 14:20:22 vancouver kernel: [ 3688.848718] do_page_fault+0x22/0x30 Apr 17 14:20:22 vancouver kernel: [ 3688.848721] page_fault+0x28/0x30 Apr 17 14:20:22 vancouver kernel: [ 3688.848723] RIP: 0033:0x55705494531e Apr 17 14:20:22 vancouver kernel: [ 3688.848725] RSP: 002b:7f3559e1f970 EFLAGS: 00010206 Apr 17 14:20:22 vancouver kernel: [ 3688.848727] RAX: 00e5 RBX: 7f3506429f10 RCX: 000a Apr 17 14:20:22 vancouver kernel: [ 3688.848729] RDX: 0005 RSI: 7f3506429000 RDI: 7f3506429f10 Apr 17 14:20:22 vancouver kernel: [ 3688.848730] RBP: 7f3573600040 R08: 7f3573600040 R09: 0004 Apr 17 14:20:22 vancouver kernel: [ 3688.848732] R10: R11: 0202 R12: 7f35064003d8 Apr 17 14:20:22 vancouver kernel: [ 3688.848733] R13: 7f3559e1fa28 R14: 7f350640 R15: Apr 17 14:20:22 vancouver kernel: [ 3688.848735] Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb Apr 17 14:20:22 vancouver kernel: [ 3688.848767] RIP: __migration_entry_wait+0x16a/0x180 RSP: 95ca01743d68 Apr 17 14:20:22 vancouver kernel: [ 3688.848770] ---[ end trace f993a2d5c1421359 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Merged upstream :D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: New Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682034] Re: linux: 4.8.0-48.51 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => 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/1682034 Title: linux: 4.8.0-48.51 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: 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: 1682037 derivatives: 1682038 -- 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/1682034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683538] [NEW] invalid opcode: 0000 [#1] SMP
Public bug reported: This is a relatively fresh installation of 17.04 on a relatively old Dell Optiplex. This message appears in /var/log/syslog: Apr 17 14:20:22 vancouver kernel: [ 3688.848621] [ cut here ] Apr 17 14:20:22 vancouver kernel: [ 3688.848628] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapo ps.h:129! Apr 17 14:20:22 vancouver kernel: [ 3688.848631] invalid opcode: [#1] SMP Apr 17 14:20:22 vancouver kernel: [ 3688.848633] Modules linked in: binfmt_misc dcdbas nvidia_uvm(POE) snd_hda_code c_hdmi coretemp kvm irqbypass serio_raw input_leds snd_usb_audio snd_hda_codec_analog snd_hda_codec_generic lpc_ich snd_hda_intel snd_hda_codec snd_usbmidi_lib snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_raw midi snd_seq snd_seq_device snd_timer snd soundcore shpchp mac_hid parport_pc ppdev lp parport ip_tables x_tables a utofs4 hid_generic nvidia_drm(POE) nvidia_modeset(POE) psmouse nvidia(POE) usbhid pata_acpi hid tg3 drm_kms_helper ptp pps_core syscopyarea sysfillrect sysimgblt fb_sys_fops drm fjes Apr 17 14:20:22 vancouver kernel: [ 3688.848668] CPU: 0 PID: 2996 Comm: Socket Thread Tainted: P OE 4.1 0.0-19-generic #21-Ubuntu Apr 17 14:20:22 vancouver kernel: [ 3688.848670] Hardware name: Dell Inc. OptiPlex 745 /0TY565, BIOS 2.3.1 05/21/2007 Apr 17 14:20:22 vancouver kernel: [ 3688.848672] task: 89e76eac2a80 task.stack: 95ca0174 Apr 17 14:20:22 vancouver kernel: [ 3688.848679] RIP: 0010:__migration_entry_wait+0x16a/0x180 Apr 17 14:20:22 vancouver kernel: [ 3688.848681] RSP: :95ca01743d68 EFLAGS: 00010246 Apr 17 14:20:22 vancouver kernel: [ 3688.848683] RAX: 000fc0048078 RBX: bb21c4402bf0 RCX: bb21c4402bf0 Apr 17 14:20:22 vancouver kernel: [ 3688.848685] RDX: 0001 RSI: 89e6d00af148 RDI: bb21c27d0a40 Apr 17 14:20:22 vancouver kernel: [ 3688.848687] RBP: 95ca01743d80 R08: 89e76ad05540 R09: 89e76ad05540 Apr 17 14:20:22 vancouver kernel: [ 3688.848688] R10: R11: 0202 R12: bb21c27d0a40 Apr 17 14:20:22 vancouver kernel: [ 3688.848690] R13: 3e09f429 R14: 95ca01743e30 R15: 89e770e9fe10 Apr 17 14:20:22 vancouver kernel: [ 3688.848692] FS: 7f3559e21700() GS:89e77bc0() knlGS:00 00 Apr 17 14:20:22 vancouver kernel: [ 3688.848694] CS: 0010 DS: ES: CR0: 80050033 Apr 17 14:20:22 vancouver kernel: [ 3688.848696] CR2: 7f3506429000 CR3: 0001ad63e000 CR4: 06f0 Apr 17 14:20:22 vancouver kernel: [ 3688.848698] Call Trace: Apr 17 14:20:22 vancouver kernel: [ 3688.848702] migration_entry_wait+0x74/0x80 Apr 17 14:20:22 vancouver kernel: [ 3688.848706] do_swap_page+0x5b3/0x770 Apr 17 14:20:22 vancouver kernel: [ 3688.848709] ? futex_wake+0x90/0x170 Apr 17 14:20:22 vancouver kernel: [ 3688.848711] handle_mm_fault+0x873/0x1360 Apr 17 14:20:22 vancouver kernel: [ 3688.848715] __do_page_fault+0x23e/0x4e0 Apr 17 14:20:22 vancouver kernel: [ 3688.848718] do_page_fault+0x22/0x30 Apr 17 14:20:22 vancouver kernel: [ 3688.848721] page_fault+0x28/0x30 Apr 17 14:20:22 vancouver kernel: [ 3688.848723] RIP: 0033:0x55705494531e Apr 17 14:20:22 vancouver kernel: [ 3688.848725] RSP: 002b:7f3559e1f970 EFLAGS: 00010206 Apr 17 14:20:22 vancouver kernel: [ 3688.848727] RAX: 00e5 RBX: 7f3506429f10 RCX: 000a Apr 17 14:20:22 vancouver kernel: [ 3688.848729] RDX: 0005 RSI: 7f3506429000 RDI: 7f3506429f10 Apr 17 14:20:22 vancouver kernel: [ 3688.848730] RBP: 7f3573600040 R08: 7f3573600040 R09: 0004 Apr 17 14:20:22 vancouver kernel: [ 3688.848732] R10: R11: 0202 R12: 7f35064003d8 Apr 17 14:20:22 vancouver kernel: [ 3688.848733] R13: 7f3559e1fa28 R14: 7f350640 R15: Apr 17 14:20:22 vancouver kernel: [ 3688.848735] Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb Apr 17 14:20:22 vancouver kernel: [ 3688.848767] RIP: __migration_entry_wait+0x16a/0x180 RSP: 95ca01743d68 Apr 17 14:20:22 vancouver kernel: [ 3688.848770] ---[ end trace f993a2d5c1421359 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: clh1886 F pulseaudio /dev/snd/controlC0: clh1886 F pulseaudio /dev/snd/controlC1: clh1886 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 16:35:04 2017 HibernationDe
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Just to confirm: Ubuntu 16.10 4.8.0-46-generic on Hyper-V Gen 2 VM on Windows Server 2016. Will check if removing the DVD drive will fix it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless
[Kernel-packages] [Bug 1682339] Re: package linux-headers-3.13.0-116 3.13.0-116.163 failed to install/upgrade: package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682339 Title: package linux-headers-3.13.0-116 3.13.0-116.163 failed to install/upgrade: package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current status `half-installed') Status in linux package in Ubuntu: Incomplete Bug description: Screen gets crashed repeatedly ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.13.0-116 3.13.0-116.163 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: neovim: Install linux-headers-3.13.0-116: Configure neovim: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: varun 3367 F pulseaudio /dev/snd/controlC1: varun 3367 F pulseaudio CRDA: country IN: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) Date: Thu Apr 13 10:36:14 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DuplicateSignature: package:linux-headers-3.13.0-116:3.13.0-116.163:package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=577af156-943f-4d6d-8660-b018d4fb0c00 InstallationDate: Installed on 2016-03-21 (387 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Inspiron 3543 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-116-generic root=UUID=2bb534c3-dee8-4ab2-9aa7-cc79e16e202d ro quiet splash video.use_native_backlight=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12 SourcePackage: linux StagingDrivers: rts5139 Title: package linux-headers-3.13.0-116 3.13.0-116.163 failed to install/upgrade: package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-03-21 (387 days ago) dmi.bios.date: 10/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682440] Re: package linux-image-4.4.0-72-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682440 Title: package linux-image-4.4.0-72-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 Status in linux package in Ubuntu: Incomplete Bug description: I'm enable to download something!! please help me! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brice 1726 F pulseaudio Date: Thu Apr 13 13:42:33 2017 DpkgHistoryLog: Start-Date: 2017-04-13 13:42:32 Commandline: apt install -f Requested-By: brice (1000) Install: linux-headers-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), linux-headers-4.4.0-72:amd64 (4.4.0-72.93, automatic), linux-image-4.4.0-66-generic:amd64 (4.4.0-66.87, automatic), linux-image-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), linux-image-extra-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.66.70, 4.4.0.72.78), linux-image-generic:amd64 (4.4.0.66.70, 4.4.0.72.78), linux-generic:amd64 (4.4.0.66.70, 4.4.0.72.78) DpkgTerminalLog: Preparing to unpack .../linux-image-4.4.0-72-generic_4.4.0-72.93_amd64.deb ... Can't locate Debconf/Client/ConfModule.pm in @INC (@INC contains: /opt/lampp/lib/perl5/site_perl/5.16.3/x86_64-linux-thread-multi /opt/lampp/lib/perl5/site_perl/5.16.3 /opt/lampp/lib/perl5/5.16.3/x86_64-linux-thread-multi /opt/lampp/lib/perl5/5.16.3 .) at /var/lib/dpkg/tmp.ci/preinst line 20. BEGIN failed--compilation aborted at /var/lib/dpkg/tmp.ci/preinst line 20. dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-72-generic_4.4.0-72.93_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 2 ErrorMessage: subprocess new pre-installation script returned error exit status 2 InstallationDate: Installed on 2016-12-28 (105 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 10f1:1a34 Importek Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite C655 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=40b59826-0bd4-49a9-89a6-5bbd8231d3fe ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-72-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.90 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd03/16/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC12U-04001W:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite C655 dmi.product.version: PSC12U-04001W dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683487] Re: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build. Upgrading from 16.10 to 17.04
*** This bug is a duplicate of bug 1683340 *** https://bugs.launchpad.net/bugs/1683340 ** This bug has been marked a duplicate of bug 1683340 zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build -- 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/1683487 Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build. Upgrading from 16.10 to 17.04 Status in zfs-linux package in Ubuntu: New Bug description: Failure after upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: zfs-dkms 0.6.5.9-5ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64) Mon Apr 17 11:33:32 CDT 2017 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.10.0-19-generic Date: Mon Apr 17 11:33:34 2017 InstallationDate: Installed on 2016-12-26 (111 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all PackageVersion: 0.6.5.9-5ubuntu4 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1683487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683509] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1683509 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683509 Title: WARNING: CPU: 0 PID: 1 at /build/linux- 1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Status in linux package in Ubuntu: Incomplete Bug description: [ cut here ] WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Modules linked in: autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ixgbe dca vxlan ip6_udp_tunnel udp_tunnel raid1 ahci ptp hpsa pps_core psmouse libahci scsi_transport_sas mdio wmi fjes CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-64-generic #85-Ubuntu 0286 15383995 880ff8feb900 813f8083 81cd1748 880ff8feb938 810812d2 88103fffd6c0 0034 024040c0 Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] __alloc_pages_slowpath.constprop.88+0x9ed/0xad0 [] ? get_page_from_freelist+0xcb/0xa50 [] ? console_unlock+0x1d5/0x550 [] __alloc_pages_nodemask+0x286/0x2a0 [] ? vprintk_emit+0x2d7/0x520 [] alloc_pages_current+0x8c/0x110 [] alloc_kmem_pages+0x19/0x90 [] kmalloc_order_trace+0x2e/0xe0 [] __kmalloc+0x22e/0x250 [] erst_reader+0x151/0x470 [] ? d_rehash+0x4c/0x60 [] pstore_get_records+0xbc/0x3e0 [] ? parse_options+0x90/0x90 [] pstore_fill_super+0xa9/0xc0 [] mount_single+0x8b/0xb0 [] pstore_mount+0x18/0x20 [] mount_fs+0x38/0x160 [] ? __alloc_percpu+0x15/0x20 [] vfs_kern_mount+0x67/0x110 [] do_mount+0x25f/0xda0 [] ? __kmalloc_track_caller+0x1b4/0x250 [] ? memdup_user+0x42/0x70 [] SyS_mount+0x9f/0x100 [] entry_SYSCALL_64_fastpath+0x16/0x71 ---[ end trace fa5b6f4ddc4df171 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683510] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1683510 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683510 Title: WARNING: CPU: 0 PID: 0 at /build/linux- 1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Status in linux package in Ubuntu: Incomplete Bug description: [ cut here ] WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-64-generic #85-Ubuntu 0086 394369744a471514 81e03e10 813f8083 81ca9210 81e03e48 810812d2 0020 81e03ec8 0001 002b Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] mach_get_cmos_time+0x186/0x1a0 [] read_persistent_clock+0xf/0x20 [] read_persistent_clock64+0x29/0x60 [] ? _set_gate.isra.2.constprop.5+0x74/0x91 [] timekeeping_init+0x23/0x1c4 [] ? _cond_resched+0x5/0x30 [] ? _cond_resched+0x5/0x30 [] ? mutex_lock+0x12/0x30 [] ? find_next_bit+0x15/0x20 [] start_kernel+0x2d4/0x4a2 [] ? early_idt_handler_array+0x120/0x120 [] x86_64_start_reservations+0x2a/0x2c [] x86_64_start_kernel+0x14a/0x16d ---[ end trace 73a280b8d116bceb ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I also have no swap. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Confirmed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: mathieu2221 F pulseaudio  /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio  /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.10.0-14-generic N/A  linux-backports-modules-4.10.0-14-generic N/A  linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I thought it was related to my system being a brand new Ryzen with ZRam and 32GB of memory (no real swap) but apparently not. A BIOS update bricked that motherboard so I'm back on my older Phenom(tm) II X4 945 with 12 GB of RAM (now no ZRAM). Just got the issue again. Now, I have *no* swap enabled at all and still got it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Confirmed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: mathieu2221 F pulseaudio  /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio  /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.10.0-14-generic N/A  linux-backports-modules-4.10.0-14-generic N/A  linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onza__3.13.0-117.164~precise1__2017-04-17_21-33-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683508] 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/1683508 Title: touchpad not working (elan_i2c invalid report id data) Status in linux package in Ubuntu: Confirmed Bug description: Sometimes upon boot mouse is not responsive. I get spammed the following in syslog every time I move the pointer: elan_i2c i2c-ELAN1000:00: invalid report id data (1) workaround: sudo rmmod elan_i2c sudo modprobe elan_i2c fixes it until next reboot, then it is a crapshoot about whether that problem will arise after boot or not. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lutostag 4214 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 16:26:12 2017 HibernationDevice: RESUME=UUID=f32bc2f0-9063-4554-8204-936f2f51ffb3 InstallationDate: Installed on 2016-09-20 (209 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 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-27 (20 days ago) dmi.bios.date: 09/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA 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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305CA 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/1683508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683509] [NEW] WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0()
Public bug reported: [ cut here ] WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Modules linked in: autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ixgbe dca vxlan ip6_udp_tunnel udp_tunnel raid1 ahci ptp hpsa pps_core psmouse libahci scsi_transport_sas mdio wmi fjes CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-64-generic #85-Ubuntu 0286 15383995 880ff8feb900 813f8083 81cd1748 880ff8feb938 810812d2 88103fffd6c0 0034 024040c0 Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] __alloc_pages_slowpath.constprop.88+0x9ed/0xad0 [] ? get_page_from_freelist+0xcb/0xa50 [] ? console_unlock+0x1d5/0x550 [] __alloc_pages_nodemask+0x286/0x2a0 [] ? vprintk_emit+0x2d7/0x520 [] alloc_pages_current+0x8c/0x110 [] alloc_kmem_pages+0x19/0x90 [] kmalloc_order_trace+0x2e/0xe0 [] __kmalloc+0x22e/0x250 [] erst_reader+0x151/0x470 [] ? d_rehash+0x4c/0x60 [] pstore_get_records+0xbc/0x3e0 [] ? parse_options+0x90/0x90 [] pstore_fill_super+0xa9/0xc0 [] mount_single+0x8b/0xb0 [] pstore_mount+0x18/0x20 [] mount_fs+0x38/0x160 [] ? __alloc_percpu+0x15/0x20 [] vfs_kern_mount+0x67/0x110 [] do_mount+0x25f/0xda0 [] ? __kmalloc_track_caller+0x1b4/0x250 [] ? memdup_user+0x42/0x70 [] SyS_mount+0x9f/0x100 [] entry_SYSCALL_64_fastpath+0x16/0x71 ---[ end trace fa5b6f4ddc4df171 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683509 Title: WARNING: CPU: 0 PID: 1 at /build/linux- 1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Status in linux package in Ubuntu: New Bug description: [ cut here ] WARNING: CPU: 0 PID: 1 at /build/linux-1hW8mg/linux-4.4.0/mm/page_alloc.c:3152 __alloc_pages_slowpath.constprop.88+0x9ed/0xad0() Modules linked in: autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ixgbe dca vxlan ip6_udp_tunnel udp_tunnel raid1 ahci ptp hpsa pps_core psmouse libahci scsi_transport_sas mdio wmi fjes CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-64-generic #85-Ubuntu 0286 15383995 880ff8feb900 813f8083 81cd1748 880ff8feb938 810812d2 88103fffd6c0 0034 024040c0 Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] __alloc_pages_slowpath.constprop.88+0x9ed/0xad0 [] ? get_page_from_freelist+0xcb/0xa50 [] ? console_unlock+0x1d5/0x550 [] __alloc_pages_nodemask+0x286/0x2a0 [] ? vprintk_emit+0x2d7/0x520 [] alloc_pages_current+0x8c/0x110 [] alloc_kmem_pages+0x19/0x90 [] kmalloc_order_trace+0x2e/0xe0 [] __kmalloc+0x22e/0x250 [] erst_reader+0x151/0x470 [] ? d_rehash+0x4c/0x60 [] pstore_get_records+0xbc/0x3e0 [] ? parse_options+0x90/0x90 [] pstore_fill_super+0xa9/0xc0 [] mount_single+0x8b/0xb0 [] pstore_mount+0x18/0x20 [] mount_fs+0x38/0x160 [] ? __alloc_percpu+0x15/0x20 [] vfs_kern_mount+0x67/0x110 [] do_mount+0x25f/0xda0 [] ? __kmalloc_track_caller+0x1b4/0x250 [] ? memdup_user+0x42/0x70 [] SyS_mount+0x9f/0x100 [] entry_SYSCALL_64_fastpath+0x16/0x71 ---[ end trace fa5b6f4ddc4df171 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683510] [NEW] WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0()
Public bug reported: [ cut here ] WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-64-generic #85-Ubuntu 0086 394369744a471514 81e03e10 813f8083 81ca9210 81e03e48 810812d2 0020 81e03ec8 0001 002b Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] mach_get_cmos_time+0x186/0x1a0 [] read_persistent_clock+0xf/0x20 [] read_persistent_clock64+0x29/0x60 [] ? _set_gate.isra.2.constprop.5+0x74/0x91 [] timekeeping_init+0x23/0x1c4 [] ? _cond_resched+0x5/0x30 [] ? _cond_resched+0x5/0x30 [] ? mutex_lock+0x12/0x30 [] ? find_next_bit+0x15/0x20 [] start_kernel+0x2d4/0x4a2 [] ? early_idt_handler_array+0x120/0x120 [] x86_64_start_reservations+0x2a/0x2c [] x86_64_start_kernel+0x14a/0x16d ---[ end trace 73a280b8d116bceb ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683510 Title: WARNING: CPU: 0 PID: 0 at /build/linux- 1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Status in linux package in Ubuntu: New Bug description: [ cut here ] WARNING: CPU: 0 PID: 0 at /build/linux-1hW8mg/linux-4.4.0/arch/x86/kernel/rtc.c:92 mach_get_cmos_time+0x186/0x1a0() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-64-generic #85-Ubuntu 0086 394369744a471514 81e03e10 813f8083 81ca9210 81e03e48 810812d2 0020 81e03ec8 0001 002b Call Trace: [] dump_stack+0x63/0x90 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_null+0x1a/0x20 [] mach_get_cmos_time+0x186/0x1a0 [] read_persistent_clock+0xf/0x20 [] read_persistent_clock64+0x29/0x60 [] ? _set_gate.isra.2.constprop.5+0x74/0x91 [] timekeeping_init+0x23/0x1c4 [] ? _cond_resched+0x5/0x30 [] ? _cond_resched+0x5/0x30 [] ? mutex_lock+0x12/0x30 [] ? find_next_bit+0x15/0x20 [] start_kernel+0x2d4/0x4a2 [] ? early_idt_handler_array+0x120/0x120 [] x86_64_start_reservations+0x2a/0x2c [] x86_64_start_kernel+0x14a/0x16d ---[ end trace 73a280b8d116bceb ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
This problem made my system mostly unuseable since upgreading to zesty (4.10.0-19). One crash every 1-4 Hours. Some workloads tend to trigger it faster (firefox + youtube) but the crash is unavoidable. Desktop usage becomes completely impossible. Normally i can sill ssh in, but only certain things work: - top works fine, I always see one kernel thread hogging cpu. Sometimes additionally a userspace process (mostly firefox). htop hangs on exit. - kill -9 on cpu hogging userspace process does not work - this seems weird - trying to reboot gracefully hangs. SysRq works. I just switched to 4.11-rc7 mainline, but its too soon to make any conclusions. I will report tomorrow. Looking through the clones of this bug this seems to happen with quite different hardware. My affected system is AMD x370 chipset with RyZen 7 1700X cpu. The system was perfectly stable with yakkety (kernel 4.8.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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Confirmed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: mathieu2221 F pulseaudio  /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio  /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.10.0-14-generic N/A  linux-backports-modules-4.10.0-14-generic N/A  linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683508] [NEW] touchpad not working (elan_i2c invalid report id data)
Public bug reported: Sometimes upon boot mouse is not responsive. I get spammed the following in syslog every time I move the pointer: elan_i2c i2c-ELAN1000:00: invalid report id data (1) workaround: sudo rmmod elan_i2c sudo modprobe elan_i2c fixes it until next reboot, then it is a crapshoot about whether that problem will arise after boot or not. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lutostag 4214 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 16:26:12 2017 HibernationDevice: RESUME=UUID=f32bc2f0-9063-4554-8204-936f2f51ffb3 InstallationDate: Installed on 2016-09-20 (209 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 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-27 (20 days ago) dmi.bios.date: 09/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA 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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683508 Title: touchpad not working (elan_i2c invalid report id data) Status in linux package in Ubuntu: Confirmed Bug description: Sometimes upon boot mouse is not responsive. I get spammed the following in syslog every time I move the pointer: elan_i2c i2c-ELAN1000:00: invalid report id data (1) workaround: sudo rmmod elan_i2c sudo modprobe elan_i2c fixes it until next reboot, then it is a crapshoot about whether that problem will arise after boot or not. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lutostag 4214 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 16:26:12 2017 HibernationDevice: RESUME=UUID=f32bc2f0-9063-4554-8204-936f2f51ffb3 InstallationDate: Installed on 2016-09-20 (209 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 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cb Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-27 (20 days ago) dmi.bios.date: 09/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA 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.:bvrUX305CA.201:bd09/11/2015:svnAS
[Kernel-packages] [Bug 1680735] onibi (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onibi__3.13.0-117.164~precise1__2017-04-17_21-14-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onza__3.13.0-117.164~precise1__2017-04-17_21-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670726] Re: h-prod does not function across cores
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670726 Title: h-prod does not function across cores Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: There is a performance problem issue with h-prod. I can see that h-prod calls are only waking hardware threads from a h-cede call when the caller is on the same core as the thread being awoken (sibling theads). For cross core prods the target thread remains in h-cede until its next decrementer interrupt. That is causing guest OS some significant dispatching delays. The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV: Fix H_PROD to actually wake the target vcpu", 2016-12-06) in v4.11-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Bug confirmed on Gigabyte GA-AB350-Gaming (non-X version) @ BIOS version F2 + Ryzen 1800X when trying to boot installation media of Ubuntu 17.04 final release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working
Hi Joseph, Thank you for the quick response. I tested this with the intel-drm-next kernel and the one you suggested and get the exact same behavior. It seems like a regression, because this was not needed on 16.04/16.10. I marked it as confirmed and added the tag, thanks you. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683445 Title: E6430 brightness control not working Status in linux package in Ubuntu: Confirmed Bug description: The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source Nouveau driver shows the brightness slider moving but does not affect the brightness. When using the kernel boot option acpi_backlight=vendor , the brightness control works. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2081 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 20:00:56 2017 HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6 InstallationDate: Installed on 2017-04-10 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Latitude E6430 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0H3MT5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683487] [NEW] zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build. Upgrading from 16.10 to 17.04
Public bug reported: Failure after upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: zfs-dkms 0.6.5.9-5ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64) Mon Apr 17 11:33:32 CDT 2017 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.10.0-19-generic Date: Mon Apr 17 11:33:34 2017 InstallationDate: Installed on 2016-12-26 (111 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all PackageVersion: 0.6.5.9-5ubuntu4 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1683487 Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build. Upgrading from 16.10 to 17.04 Status in zfs-linux package in Ubuntu: New Bug description: Failure after upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: zfs-dkms 0.6.5.9-5ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64) Mon Apr 17 11:33:32 CDT 2017 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.10.0-19-generic Date: Mon Apr 17 11:33:34 2017 InstallationDate: Installed on 2016-12-26 (111 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all PackageVersion: 0.6.5.9-5ubuntu4 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1683487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks
Just tested under: 4.11.0-041100rc7-generic The problem is the same. I have always had this problem under Linux, but started using on these notebooks since kernel 4.8. ** Tags added: kernel-bug-exists-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/1683277 Title: Mute key LED does not work on HP notebooks Status in linux package in Ubuntu: Confirmed Bug description: Description of problem: The F6/mute key on the keyboard of HP notebooks often has a built in LED indicator to show if the sound is muted. The LED state is never toggled. It will just retain its state, even though the audio is succesfully muted/unmuted. Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream 11 from 2016. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Press mute key on HP laptop Actual results: Mute state in software toggles, LED in mute key does not. Expected results: Mute state in software and LED in mute key toggle. Additional info: This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stevenh1659 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 17 11:02:20 2017 HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2 InstallationDate: Installed on 2016-09-13 (215 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81CC dmi.board.vendor: HP dmi.board.version: KBC Version 60.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onza (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onza__3.13.0-117.164~precise1__2017-04-17_19-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Thanks a lot Andrei, Tested on a lubuntu 17:04 fresh install. It almost works, the audio plays nicely, but only when the pulseaudio volume control is open, as soon as it's closed it looks like the default audio device is switched to another device. Added this line to /etc/pulse/default.pa set-default-sink alsa_output.platform-cht- cx2072x.HiFi__hw_chtcx2072x_0__sink The kernel is not selected by default since the version supplied with ubuntu is more recent. Touchscreen is not working, but maybe is Lubuntu to blame, since in my previuos Xubuntu install i got it working. Thanks Again, Marco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.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: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs
I built X, Y and Z test kernels with the requested commits. The test kernels can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1682665/ Xenial only needed the second two commits. The first two were already included as SAUCE patches. Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682665 Title: [Hyper-V] PCI passthrough fixes for 32 or more CPUs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: The following set of patches are needed for SR-IOV on larger VM sizes on Hyper-V, especially with more than 32 CPUs. Some of these patches were already pulled in as SAUCE for SR-IOV in Azure previously. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=22e2495b76dbe398540faf355a541b10faad33b9 Merge branch 'pci/host-hv' into next * pci/host-hv: PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs PCI: hv: Lock PCI bus on device eject PCI: hv: Properly handle PCI bus remove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683091] Re: The whole system froze for something like 30 seconds, then a process got killed
Do you have a way to reproduced this bug, or was it a one time event? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683091 Title: The whole system froze for something like 30 seconds, then a process got killed Status in linux package in Ubuntu: Incomplete Bug description: Upgraded from xenial to zesty recently. I was using a Firefox instance, one which is a part of Tor Browser Bundled. First, the application window grayed out, then the whole system froze for something like 30 seconds (I tried to switch to VT1 to no avail), then the process got killed. Well, not exactly killed. The grayed-out window is still there, `xprop | grep PID` and clicking on it gives: ``` _NET_WM_PID(CARDINAL) = 13 ``` PID 13 is a child of kthreadd: ``` $ ps -A | awk '$1 == "13" { print }'    13 ?00:00:00 cpuhp/1 ``` And this is how the relevant part of `ps -AH` with the "killed" process looks like: ```  5709 pts/11 00:00:00 firejail  5710 pts/11 00:00:00 firejail  5725 pts/11 00:00:00 bash  5736 pts/11 00:56:49 firefox  5769 pts/11 00:00:24 tor ``` EDIT: Launchpad doesn't preserve whitespace apparently, so I'm adding the output above as ps.log. I checked syslog and dmesg. Both of them have an interesting and identical message, which I add as dmesg.log. I also add the output of `cat /proc/version_signature` as version.log. I don't think `sudo lspci -vnvn` is relevant here, so I'm not gonna share it unless absolutely necessary. The crashed process will be there for something like 2 or 3 days at least (I don't restart my laptop often), so feel free to ask me to manipulate or query it somehow, if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666197] Re: POWER9 : Enable Stop 0-2 with ESL=EC=0
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666197 Title: POWER9 : Enable Stop 0-2 with ESL=EC=0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: In Linux 4.10-rc8, the implementation to enable the "stop" instruction has the following shortcomings: a) The code hand-codes the values for ESL, EC, TR, MTL bits of PSSCR and uses only the RL field from the firmware. While this is not incorrect, since the hand-coded values are legitimate, it is not a very flexible design since the firmware has the capability to communicate these values via the "ibm,cpu-idle-state-psscr" and "ibm,cpu-idle-state-psscr-mask" properties. In case where the firmware provides values for these fields that is different from the hand-coded values, the current code will not work as intended. b) Due to issue a), the current code assumes that ESL=EC=1 for all the stop states and hence the wakeup from the stop instruction will happen at 0x100, the system-reset vector which also results in GPR state loss. However, the ISA v3.0 allows the ESL=EC=0 behaviour where the corresponding stop-states lose no GPR state and wakes up from the subsequent instruction. The code in 4.10-rc8 doesn't support these light-weight stop modes. The following commits in the "next" branch of the powerpc-linux git tree (git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git) address these issues. These patches are needed in 17.04 to enable light-weight stop modes 1) commit 823b7bd5156a93872d9561b3f033dfe5cb80204e, powernv:idle: Add IDLE_STATE_ENTER_SEQ_NORET macro 2)commit dd34c74c97b6c3ed1ac7caec0b46267142659aff, powernv:stop: Rename pnv_arch300_idle_init to pnv_power9_idle_init 3)commit 9e9fc6f00a54f7064dc681ac187be6498d566a4f, cpuidle:powernv: Add helper function to populate powernv idle states 4)commit 09206b600c76f20984e80d99f3b5343c79332a97, powernv: Pass PSSCR value and mask to power9_idle_stop 5)commit b48ff52043f489d594b989b318c120ca340a2e41, Documentation:powerpc: Add device-tree bindings for power-mgt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670800] Re: Power9 kernel: add virtualization patches
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670800 Title: Power9 kernel: add virtualization patches Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Dear Canonical, Please add the following patches for POWER9: From powerpc/next tree: cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of radix MMU under hypervisor on POWER9 6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9 architected mode to cputable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674325] Re: POWER9: Additional patches for TTY and CPU_IDLE
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674325 Title: POWER9: Additional patches for TTY and CPU_IDLE Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Hello Canonical, There are two additional bug hitting our POWER9, and we would like to have them fixed, please: [TTY] tty: Fix ldisc crash on reopened tty - https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h =tty-next&id=71472fa9c52b1da27663c275d416d8654b905f05 [CPU IDLE] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration - http://patchwork.ozlabs.org/patch/740414/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onibi (i386) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onibi__3.13.0-117.164~precise1__2017-04-17_19-01-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onza (i386) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onza__3.13.0-117.164~precise1__2017-04-17_18-55-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683458] 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/1683458 Title: kern.log flooded with xhci-hcd warning message Status in linux package in Ubuntu: Confirmed Bug description: Appears to be identical to #1541997 but submitting here using ubuntu- bug for completeness This message repeats forever, rapidly making the log file huge. Apr 17 11:42:31 gvlt kernel: [255517.557491] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557629] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557761] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557892] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 3857 F pulseaudio Date: Mon Apr 17 11:48:29 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-17 (304 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic.efi.signed root=UUID=e22b40a4-a1aa-49d7-963c-121a4c1fb4b3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 08R8KJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn08R8KJ:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1541997] Re: dmesg flooded with xhci_hcd warnings "WARN Event TRB for slot 1 ep 8 with no TDs queued?"
Same problem on Dimension 5510. Submitted but with ubuntu-bug linux into bug report #1683458 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1541997 Title: dmesg flooded with xhci_hcd warnings "WARN Event TRB for slot 1 ep 8 with no TDs queued?" Status in linux package in Ubuntu: Expired Bug description: I am running vmware, hosting a Windows 10 guest, relaying USB smartcard reader and see a flood of following warnings in dmesg: "xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 8 with no TDs queued?" I only presume they are related to vmware/usb smartcard reader, I can't be sure. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-27-generic 4.2.0-27.32 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: cromo 2748 F...m pulseaudio /dev/snd/controlC1: cromo 2748 F pulseaudio /dev/snd/controlC0: cromo 2748 F pulseaudio /dev/snd/timer: cromo 2748 f pulseaudio CurrentDesktop: GNOME Date: Thu Feb 4 14:19:30 2016 HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df InstallationDate: Installed on 2013-04-24 (1016 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: Dell Inc. Latitude E6230 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-28 (98 days ago) dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0GWYCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/20/2013:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0GWYCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683458] [NEW] kern.log flooded with xhci-hcd warning message
Public bug reported: Appears to be identical to #1541997 but submitting here using ubuntu-bug for completeness This message repeats forever, rapidly making the log file huge. Apr 17 11:42:31 gvlt kernel: [255517.557491] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557629] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557761] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557892] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 3857 F pulseaudio Date: Mon Apr 17 11:48:29 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-17 (304 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic.efi.signed root=UUID=e22b40a4-a1aa-49d7-963c-121a4c1fb4b3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 08R8KJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn08R8KJ:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1683458 Title: kern.log flooded with xhci-hcd warning message Status in linux package in Ubuntu: Confirmed Bug description: Appears to be identical to #1541997 but submitting here using ubuntu- bug for completeness This message repeats forever, rapidly making the log file huge. Apr 17 11:42:31 gvlt kernel: [255517.557491] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557629] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557761] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? Apr 17 11:42:31 gvlt kernel: [255517.557892] xhci_hcd :00:14.0: WARN Event TRB for slot 20 ep 2 with no TDs queued? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 3857 F pulseaudio Date: Mon Apr 17 11:48:29 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-17 (304 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 MachineType: Dell Inc. Precision 5510 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic.efi.signed root=UUID=e22b40a4-a1aa-49d7-963c-121a4c1fb4b3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 SourcePackage: linux Upgrade
[Kernel-packages] [Bug 1683110] Re: ath9k crashes the system
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Zesty) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Zesty) 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/1683110 Title: ath9k crashes the system Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: After upgraded to 17.04 from 16.10, my system cannot boot into the GUI anymore with kernel 4.10.0. I can boot it with the old kernel 4.8.0 from 16.10. When boot with 4.10.0 kernel, the system is crashed. I can see that ath9k caused it from dmesg. Also this bug report is created with atk9k disabled so if there is anything missing, please ask so I could include it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Â USERPID ACCESS COMMAND Â /dev/snd/controlC0: quang 2038 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Apr 16 13:57:17 2017 HibernationDevice: RESUME=UUID=d756d907-93fa-4ca5-971e-e28ffbc15946 InstallationDate: Installed on 2016-10-14 (183 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IwConfig: Â enp4s0f2 no wireless extensions. Â lono wireless extensions. MachineType: Acer EA40_CX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=a5def0bc-8223-4d88-bbca-6fc32fcec07f ro quiet splash vt.handoff=7 RelatedPackageVersions: Â linux-restricted-modules-4.10.0-19-generic N/A Â linux-backports-modules-4.10.0-19-generic N/A Â linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.04 dmi.board.name: EA40_CX dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd09/18/2013:svnAcer:pnEA40_CX:pvrV2.04:rvnAcer:rnEA40_CX:rvrV2.04:cvnAcer:ct9:cvrV2.04: dmi.product.name: EA40_CX dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683157] Re: Ethernet, WiFi, touchpad/trackpoint not detected on boot
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683157 Title: Ethernet, WiFi, touchpad/trackpoint not detected on boot Status in linux package in Ubuntu: Incomplete Bug description: This is a regression from Ubuntu 16.10. I have upgraded this Lenovo X300 yesterday, and noticed this bug: Steps to reproduce: * turn laptop off completely, unplug power * plug in power * turn on laptop, and boot Xubuntu 17.04 * Login Expected results: * Connected to internet, able to use touchpad/trackpoint Actual results: * At least 1 time out of 4 a lot of devices are not detected during boot * There is no WiFi device * There is no touchpad/trackpoint device (plugging in an external mouse works) * Keyboard still works Workaround: * sudo udevadm trigger * all devices get detected and working Also reproducible when running on battery. Note: I've only seen this bug on this device, my 2 other devices (a Dell Latitude E7470 laptop, and an AMD FX desktop) do not have this bug. See attached tarball for lspci/lsusb/dmesg/journal outputs from a good, and 3 bad boots. Here is what happens after udevadm trigger, but the kernel should be able to detect all this on its own during boot, without needing a manual udevadm trigger! [ 244.902251] pps_core: LinuxPPS API ver. 1 registered [ 244.902253] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 244.930231] PTP clock support registered [ 244.954346] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 244.954349] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 244.954711] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 244.966799] FUJITSU Extended Socket Network Device Driver - version 1.2 - Copyright (c) 2015 FUJITSU LIMITED [ 245.345396] Bluetooth: Core ver 2.22 [ 245.345430] NET: Registered protocol family 31 [ 245.345432] Bluetooth: HCI device and connection manager initialized [ 245.345438] Bluetooth: HCI socket layer initialized [ 245.345443] Bluetooth: L2CAP socket layer initialized [ 245.345455] Bluetooth: SCO socket layer initialized [ 245.478228] usbcore: registered new interface driver btusb [ 245.681594] media: Linux media interface: v0.10 [ 245.717154] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:1f:e2:1c:46:e5 [ 245.717159] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection [ 245.718968] e1000e :00:19.0 eth0: MAC: 6, PHY: 6, PBA No: 1008FF-0FF [ 245.719439] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 245.728940] snd_hda_intel :00:1b.0: probe_mask set to 0x1 for device 17aa:20ac [ 245.731649] ACPI Warning: SystemIO range 0x1028-0x102F conflicts with OpRegion 0x1000-0x107F (\_SB.PCI0.LPC.PMIO) (20160930/utaddress-247) [ 245.731659] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 245.731666] ACPI Warning: SystemIO range 0x11B0-0x11BF conflicts with OpRegion 0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) (20160930/utaddress-247) [ 245.731673] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 245.731675] ACPI Warning: SystemIO range 0x1180-0x11AF conflicts with OpRegion 0x1180-0x11BF (\_SB.PCI0.LPC.LPIO) (20160930/utaddress-247) [ 245.731682] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 245.731683] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 245.811261] Linux video capture interface: v2.00 [ 245.852532] Non-volatile memory driver v1.3 [ 245.859889] thinkpad_acpi: ThinkPad ACPI Extras v0.25 [ 245.859891] thinkpad_acpi: http://ibm-acpi.sf.net/ [ 245.859893] thinkpad_acpi: ThinkPad BIOS 7TET36WW (1.10 ), EC 7THT16WW-1.01 [ 245.859895] thinkpad_acpi: Lenovo ThinkPad X300,
[Kernel-packages] [Bug 1683165] Re: suspend/resume yields blank screen on NVIDIA desktop
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683165 Title: suspend/resume yields blank screen on NVIDIA desktop Status in linux package in Ubuntu: Incomplete Bug description: On my desktop when I set "System settings > Power > Suspend when inactive for" to any time (5 minutes, say), and wait, Ubuntu suspends. When I power my desktop back on, it boots without the usual chatter on the screen and the screen stays entirely blank (the monitor is in power-save mode). At that point the only workaround is to force a reboot by holding down the power button for 4 seconds, and go through the ordinary boot process. This appears to be the same symptoms as Bug#1283938, the last comment of which says "file a bug by running 'ubuntu-bug linux'", which is what I've done here. I have had the problem for years but have not reported it until today. My desktop has an Asus M4N78 Pro motherboard, which uses an NVIDIA GeForce 8300 chipset. lspci reports the graphics controller as "NVIDIA Corporation C77 [GeForce 8300] (rev a2)". "Software & Updates" says I am using "NVIDIA legacy binary driver - version 304.135 from nvidia-304 (proprietary)". As discussed in Bug#1639180 comment#65, I cannot use the latest NVIDIA driver as it has so many artifacts on the screen that it is unusable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-72-generic 4.4.0-72.93 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eggert 1825 F pulseaudio /dev/snd/controlC1: eggert 1825 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 16 09:38:00 2017 HibernationDevice: RESUME=UUID=433ca071-21cd-44b7-9b81-2b73c0463790 InstallationDate: Installed on 2014-04-27 (1084 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=0d7c67e2-db5b-493a-890b-90121ad2ee20 ro quiet splash acpi_enforce_resources=lax RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (358 days ago) dmi.bios.date: 07/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N78 PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683277] Re: Mute key LED does not work on HP notebooks
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683277 Title: Mute key LED does not work on HP notebooks Status in linux package in Ubuntu: Incomplete Bug description: Description of problem: The F6/mute key on the keyboard of HP notebooks often has a built in LED indicator to show if the sound is muted. The LED state is never toggled. It will just retain its state, even though the audio is succesfully muted/unmuted. Tested with HP Envy 15 from 2015. HP Stream 11 from 2015 and HP Stream 11 from 2016. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Press mute key on HP laptop Actual results: Mute state in software toggles, LED in mute key does not. Expected results: Mute state in software and LED in mute key toggle. Additional info: This happens on kernel 4.8, 4.9 and 4.10. I have not tested any other versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stevenh1659 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 17 11:02:20 2017 HibernationDevice: RESUME=UUID=2d246125-abf7-4945-9542-45b25fb8fcb2 InstallationDate: Installed on 2016-09-13 (215 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81CC dmi.board.vendor: HP dmi.board.version: KBC Version 60.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/13/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683340] Re: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1683340 Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 17.04 Package: zfs-dkms 0.6.5.9-5ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64) luni 17 aprilie 2017, 14:43:07 +0300 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.10.0-19-generic Date: Mon Apr 17 14:43:08 2017 InstallationDate: Installed on 2016-10-19 (180 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all PackageVersion: 0.6.5.9-5ubuntu4 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1683340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683445] Re: E6430 brightness control not working
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683445 Title: E6430 brightness control not working Status in linux package in Ubuntu: Incomplete Bug description: The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source Nouveau driver shows the brightness slider moving but does not affect the brightness. When using the kernel boot option acpi_backlight=vendor , the brightness control works. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2081 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 20:00:56 2017 HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6 InstallationDate: Installed on 2017-04-10 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Latitude E6430 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0H3MT5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683441] Re: systemd-resolved doesn't work after suspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683441 Title: systemd-resolved doesn't work after suspend Status in linux package in Ubuntu: Incomplete Bug description: After suspend/resume DNS name resolution stop working. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] Re: multitouch gestures support is broken
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Zesty) 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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680735] onza (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/3.13.0-117.164~precise1-generic/onza__3.13.0-117.164~precise1__2017-04-17_18-25-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1680735 Title: linux-lts-trusty: 3.13.0-117.164~precise1 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: New 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 -- kernel-stable-master-bug: 1680733 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/1680735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667081] Re: Nvlink2: Additional patches
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667081 Title: Nvlink2: Additional patches Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: Hello Canonical, Could you please integrate the patches to enable NVLink2 in Ubuntu? They are, so far: commit 616badd2fb499320d3ac3b54462f55dededd0e0f Author: Alistair Popple Date: Tue Jan 10 15:41:44 2017 +1100 powerpc/powernv: Use OPAL call for TCE kill on NVLink2 Add detection of NPU2 PHBs. NPU2/NVLink2 has a different register layout for the TCE kill register therefore TCE invalidation should be done via the OPAL call rather than using the register directly as it is for PHB3 and NVLink1. This changes TCE invalidation to use the OPAL call in the case of a NPU2 PHB model. commit 1d0761d2557d1540727723e4f05395d53321d555 Author: Alistair Popple Date: Wed Dec 14 13:36:51 2016 +1100 powerpc/powernv: Initialise nest mmu POWER9 contains an off core mmu called the nest mmu (NMMU). This is used by other hardware units on the chip to translate virtual addresses into real addresses. The unit attempting an address translation provides the majority of the context required for the translation request except for the base address of the partition table (ie. the PTCR) which needs to be programmed into the NMMU. This patch adds a call to OPAL to set the PTCR for the nest mmu in opal_init(). These patches are, still, in the powerpc-next tree. == Comment: #2 - Breno Henrique Leitao - 2017-02-22 13:33:59 == In order to support NVLink2, the memory hotplugs should be applied also, they are: 0d0a4bc powerpc/mm: unstub radix__vmemmap_remove_mapping() 4b5d62c powerpc/mm: add radix__remove_section_mapping() 6cc2734 powerpc/mm: add radix__create_section_mapping() b5200ec powerpc/mm: refactor radix physical page mapping 32b53c0 powerpc/mm: Fix memory hotplug BUG() on radix c3352cb dt: add documentation of "hotpluggable" memory property 41a9ada of/fdt: mark hotpluggable memory 114cf3c mm: enable CONFIG_MOVABLE_NODE on non-x86 arches 39fa104 mm: remove x86-only restriction of movable_node 4a3bac4 powerpc/mm: allow memory hotplug into a memoryless node Note that you need to set CONFIG_MOVABLE_NODE=y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1669023] Re: Kernel: Fix Transactional memory config typo
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1669023 Title: Kernel: Fix Transactional memory config typo Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Canonical, Please include the following fix on 16.10. This typo is causing some issue on TM. The patches that causes this problem is ec2a04841b785373a6379af66032201a2b90922b on yakkety-ubuntu repo. commit 39715bf972ed4fee18fe5409609a971fb16b1771 Author: Valentin Rothberg Date: Wed Oct 5 07:57:26 2016 +0200 powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state() It should be ALTIVEC, not ALIVEC. Cyril explains: If a thread performs a transaction with altivec and then gets preempted for whatever reason, this bug may cause the kernel to not re-enable altivec when that thread runs again. This will result in an altivec unavailable fault, when that fault happens inside a user transaction the kernel has no choice but to enable altivec and doom the transaction. The result is that transactions using altivec may get aborted more often than they should. The difficulty in catching this with a selftest is my deliberate use of the word may above. Optimisations to avoid FPU/altivec/VSX faults mean that the kernel will always leave them on for 255 switches. This code prevents the kernel turning it off if it got to the 256th switch (and userspace was transactional). Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware transactional memory in use") Reviewed-by: Cyril Bur Signed-off-by: Valentin Rothberg Signed-off-by: Michael Ellerman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670247] Comment bridged from LTC Bugzilla
--- Comment From cls...@us.ibm.com 2017-04-17 14:33 EDT--- (In reply to comment #14) > This bug is awaiting verification that the kernel in -proposed solves the > problem. Please test the kernel and update this bug with the results. If the > problem is solved, change the tag 'verification-needed-yakkety' to > 'verification-done-yakkety'. If the problem still exists, change the tag > 'verification-needed-yakkety' to 'verification-failed-yakkety'. > > If verification is not done by 5 working days from today, this fix will be > dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Thank you! Hi Canonical Which yakkety kernel is the one with the fix? from looking at git it maybe in 4.8.0-47.50 but when I check the proposed kernel I only see until 4.8.0-46-generic. Can you confirm? thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670247 Title: Ubuntu 16.10: Network checksum fixes needed for IPoIB for Mellanox CX4/CX5 card Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Carol L. Soto - 2017-03-03 22:23:11 == ---Problem Description--- Mellanox CX4/CX5 IB if running IPoIB in connected mode, it does not have the hw checksum so when running IPoIB in power system the performance is low. with iperf and 4 threads we get [ 8] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48536 [ 4] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48538 [ 5] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48540 [ 6] local 44.44.44.44 port 5001 connected with 44.44.44.45 port 48542 [ 8] 0.0-10.0 sec 9.07 GBytes 7.79 Gbits/sec [ 4] 0.0-10.0 sec 9.16 GBytes 7.87 Gbits/sec [ 5] 0.0-10.0 sec 9.13 GBytes 7.84 Gbits/sec [ 6] 0.0-10.0 sec 9.18 GBytes 7.88 Gbits/sec [SUM] 0.0-10.0 sec 36.5 GBytes 31.4 Gbits/sec if we add the following patches: From 68201fbbb04a030864f8560b05d43d8019f7f8df Mon Sep 17 00:00:00 2001 From: Michael Ellerman Date: Thu, 11 Aug 2016 16:03:14 +1000 Subject: powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS From b492f7e4e07a28e706db26cf4943bb0911435426 Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:10:55 +1100 Subject: powerpc/64: Fix checksum folding in csum_tcpudp_nofold and ip_fast_csum_nofold From d4fde568a34a93897dfb9ae64cfe9dda9d5c908c Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Thu, 3 Nov 2016 16:15:42 +1100 Subject: powerpc/64: Use optimized checksum routines on little-endian then I can get with iperf [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 23.0 GBytes 19.7 Gbits/sec [ 6] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 5] 0.0-10.0 sec 22.9 GBytes 19.7 Gbits/sec [ 7] 0.0-10.0 sec 22.9 GBytes 19.6 Gbits/sec [SUM] 0.0-10.0 sec 91.7 GBytes 78.7 Gbits/sec Contact Information = Carol Soto/cls...@us.ibm.com ---uname output--- 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:22:53 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Need a power system and Mellanox CX4 IB card. Machine Type = P8 ---Steps to Reproduce--- just run iperf with IPoIB in connected mode and will see aroung 30Gbits/sec. If we add the patches then we can get more than 70Gbits/sec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic
Same test setup as above, but using yakkety with kernel 4.8.0-46-generic, reproduces the kernel oops. After upgrading to kernel 4.8.0-48-generic, the kernel oops no longer happens when modprobing or rmmoding br_netfilter. ** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672470 Title: ip_rcv_finish() NULL pointer kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] When using iptables rules affecting bridge traffic, and if affected traffic is flowing through bridge while br_netfilter module is loaded or unloaded, a kernel panic may occur. [Test Case] It's difficult to reproduce because of a very small race condition window during br_netfilter load/unload when the module is receiving traffic but has not yet registered its hooks (or, has unregistered its hooks but still has traffic it's processing). A system must be set up using a bridge, and iptable netfilter rules must be set up to process the bridge traffic. Then the system should be rebooted until the problem occurs, or the br_netfilter module should be loaded/unloaded until the problem occurs. [Regression Potential] Changing how the br_netfilter module switches its fake dst for a real dst may, if done incorrectly, result in more kernel panics if other code tries to process the br_netfilter module's fake dst. [Other Info] The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When the skb leaves the bridge, it removes the fake dst and places a real dst onto it. However, it uses a hook to do this, and when the br_netfilter module is unloading it unregisters that hook. Any skbs that are currently being processed in the bridge by the br_netfilter module, but that leave the bridge after the hook is unregistered (or, during br_netfilter module load, before the hook is registered) will still have the fake dst; when other code then tries to process that dst, it causes a kernel panic because the dst is invalid. Recent upstream discussion: https://www.spinics.net/lists/netdev/msg416912.html Upstream patch: https://patchwork.ozlabs.org/patch/738275/ upstream commit is a13b2082ece95247779b9995c4e91b4246bed023 example panic report: [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null) [ 214.612199] IP: [< (null)>] (null) [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca procmemro(O) nokeyctl(O) noptrace(O) [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1 [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.13a.0.0713160937 07/13/16 [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 8810392b [ 215.331207] RIP: 0010:[<>] [< (null)>] (null) [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286 [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: [ 215.569836] RDX: RSI: RDI: 881011067100 [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0 [ 215.740629] R10: R11: R12: 881018917dce [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078 [ 215.911432] FS: () GS:88103fec() knlGS: [ 216.008274] CS: 0010 DS: ES: CR0: 80050033 [ 216.077032] CR2: CR3: 001011b9d000 CR4: 001406e0 [ 216.162430] Stack: [ 216.186461] 8157d7f9 881011067100 881018917dce 88101163 [ 216.275407] 81c9be00 88103fec3918 8157e0db [ 216.364352] [ 216.453301] Call Trace: [ 216.482536] [ 216.505533] [] ? ip_rcv_finish+0x99/0x320 [ 216.575442] [] ip_rcv+0x25b/0x370 [ 216.634842] [] __netif_receive_skb_core+0x2cb/0xa20 [ 216.712965] [] __netif_receive_skb+0x18/0x60 [ 216.783801] [] netif_receive_skb_internal+0x23/0x80 [ 216.861921] [] netif_receive_skb+0x1c/0x70 [ 216.930686] [] br_handle_frame_finish+0x1b9/0x5b0 [bridge] [ 21
[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs
** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Zesty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682665 Title: [Hyper-V] PCI passthrough fixes for 32 or more CPUs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: The following set of patches are needed for SR-IOV on larger VM sizes on Hyper-V, especially with more than 32 CPUs. Some of these patches were already pulled in as SAUCE for SR-IOV in Azure previously. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=22e2495b76dbe398540faf355a541b10faad33b9 Merge branch 'pci/host-hv' into next * pci/host-hv: PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs PCI: hv: Lock PCI bus on device eject PCI: hv: Properly handle PCI bus remove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] 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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683441] 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/1683441 Title: systemd-resolved doesn't work after suspend Status in linux package in Ubuntu: Confirmed Bug description: After suspend/resume DNS name resolution stop working. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683441/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683445] 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/1683445 Title: E6430 brightness control not working Status in linux package in Ubuntu: Confirmed Bug description: The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source Nouveau driver shows the brightness slider moving but does not affect the brightness. When using the kernel boot option acpi_backlight=vendor , the brightness control works. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2081 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 20:00:56 2017 HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6 InstallationDate: Installed on 2017-04-10 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Latitude E6430 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0H3MT5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1672470] Re: ip_rcv_finish() NULL pointer kernel panic
With a virsh guest installed with standard xenial, using the 4.4.0-72-generic kernel, I created a bridge and attached the virtio interface to it. I then started iperf3 -s on the guest, and started iperf3 -c GUESTIP -t 300 on the host, to create continuous traffic to the guest. Then I added a simple iptables rule: $ sudo iptables -A INPUT -s 192.168.122.0/24 -j MARK --set-mark 1234 that rule matches all incoming iperf3 packets. Then, simply modprobing the br_netfilter module reproduces this kernel oops. I then added xenial-proposed to the apt sources, and upgraded the kernel to version 4.4.0-74-generic, and re-ran the above test, which allowed the br_netfilter module to be loaded with no kernel oops or other problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1672470 Title: ip_rcv_finish() NULL pointer kernel panic Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] When using iptables rules affecting bridge traffic, and if affected traffic is flowing through bridge while br_netfilter module is loaded or unloaded, a kernel panic may occur. [Test Case] It's difficult to reproduce because of a very small race condition window during br_netfilter load/unload when the module is receiving traffic but has not yet registered its hooks (or, has unregistered its hooks but still has traffic it's processing). A system must be set up using a bridge, and iptable netfilter rules must be set up to process the bridge traffic. Then the system should be rebooted until the problem occurs, or the br_netfilter module should be loaded/unloaded until the problem occurs. [Regression Potential] Changing how the br_netfilter module switches its fake dst for a real dst may, if done incorrectly, result in more kernel panics if other code tries to process the br_netfilter module's fake dst. [Other Info] The br_netfilter module processes packets traveling through its bridge, and while processing each skb it places a special fake dst onto the skb. When the skb leaves the bridge, it removes the fake dst and places a real dst onto it. However, it uses a hook to do this, and when the br_netfilter module is unloading it unregisters that hook. Any skbs that are currently being processed in the bridge by the br_netfilter module, but that leave the bridge after the hook is unregistered (or, during br_netfilter module load, before the hook is registered) will still have the fake dst; when other code then tries to process that dst, it causes a kernel panic because the dst is invalid. Recent upstream discussion: https://www.spinics.net/lists/netdev/msg416912.html Upstream patch: https://patchwork.ozlabs.org/patch/738275/ upstream commit is a13b2082ece95247779b9995c4e91b4246bed023 example panic report: [ 214.518262] BUG: unable to handle kernel NULL pointer dereference at (null) [ 214.612199] IP: [< (null)>] (null) [ 214.672744] PGD 0 [ 214.696887] Oops: 0010 [#1] SMP [ 214.735697] Modules linked in: br_netfilter(+) tun 8021q bridge stp llc bonding iTCO_wdt iTCO_vendor_support tpm_tis tpm kvm_intel kvm irqbypass sb_edac edac_core ixgbe mdio ipmi_si ipmi_msghandler lpc_ich mfd_core mousedev evdev igb dca procmemro(O) nokeyctl(O) noptrace(O) [ 215.029240] CPU: 34 PID: 0 Comm: swapper/34 Tainted: G O 4.4.39 #1 [ 215.116720] Hardware name: Cisco Systems Inc UCSC-C220-M3L/UCSC-C220-M3L, BIOS C220M3.2.0.13a.0.0713160937 07/13/16 [ 215.241644] task: 882038fb4380 ti: 8810392b task.ti: 8810392b [ 215.331207] RIP: 0010:[<>] [< (null)>] (null) [ 215.420877] RSP: 0018:88103fec3880 EFLAGS: 00010286 [ 215.484436] RAX: 881011631000 RBX: 881011067100 RCX: [ 215.569836] RDX: RSI: RDI: 881011067100 [ 215.655234] RBP: 88103fec38a8 R08: 0008 R09: 8810116300a0 [ 215.740629] R10: R11: R12: 881018917dce [ 215.826030] R13: 81c9be00 R14: 81c9be00 R15: 881011630078 [ 215.911432] FS: () GS:88103fec() knlGS: [ 216.008274] CS: 0010 DS: ES: CR0: 80050033 [ 216.077032] CR2: CR3: 001011b9d000 CR4: 001406e0 [ 216.162430] Stack: [ 216.186461] 8157d7f9 881011067100 881018917dce 88101163 [ 216.275407] 81c9be00 88103fec3918 8157e0db [ 216.364352] [ 216.453301] Call Trace: [ 2
[Kernel-packages] [Bug 1683447] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863770/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863766/+files/JournalErrors.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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682230] Re: Wifi usb stick and cordless keyboard and mouse freeze system
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.61 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** 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/1682230 Title: Wifi usb stick and cordless keyboard and mouse freeze system Status in linux package in Ubuntu: Incomplete Bug description: Hello, For kernels 4.4, using a usb wifi dongle (0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter) and a cordless mouse/keyboard (1d57:fa20 Xenta ) freeze the system. With 4.8.0-36 kernel, all is fine. With update 4.8.0-46, the system freeze. lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alain 1671 F pulseaudio /dev/snd/controlC0: alain 1671 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8185182f-9ef4-421b-afca-6589e86759dc InstallationDate: Installed on 2017-04-09 (3 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=4d6d30b5-6ba4-4b58-b88f-62b2ea234e34 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo video _MarkForUpload: True dmi.bios.date: 01/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863769/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863767/+files/Lspci.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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863768/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863762/+files/AlsaInfo.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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863776/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863773/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863775/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863772/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863771/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863774/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863763/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863764/+files/CurrentDmesg.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/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1683447/+attachment/4863765/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683447] [NEW] multitouch gestures support is broken
Public bug reported: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.17 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected zesty ** Tags added: apport-collected zesty ** Description changed: - After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. - Looks like they doesn't supported any more. Why? + After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? + --- + ApportVersion: 2.20.4-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: bob1644 F pulseaudio + CurrentDesktop: Unity:Unity7 + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-04-17 (0 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai + Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Acer Aspire ES1-331 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-19-generic N/A + linux-backports-modules-4.10.0-19-generic N/A + linux-firmware 1.164 + Tags: zesty + Uname: Linux 4.10.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/30/2016 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V1.17 + dmi.board.name: Aspire ES1-331 + dmi.board.vendor: Acer + dmi.board.version: V1.17 + dmi.chassis.type: 10 + dmi.chassis.vendor: Acer + dmi.chassis.version: V1.17 + dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17: + dmi.product.name: Aspire ES1-331 + dmi.product.version: V1.17 + dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683447 Title: multitouch gestures support is broken Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 17.04 3- and 4-fingers gestures stop working. Looks like they doesn't supported any more. Why? --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1644 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f
[Kernel-packages] [Bug 1560473] Re: Fan doesn't work
Aspire ES1-331, bios 1.17, Ubuntu 17.04. Fan works properly. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1560473 Title: Fan doesn't work Status in linux package in Ubuntu: Fix Released Bug description: There is no fan support for this hardware. Fan speed changing only on reboot and stay the same until reboot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-34-generic 4.2.0-34.39 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob3618 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 22 18:25:27 2016 HibernationDevice: RESUME=UUID=0d193a72-b3ef-44a7-92c8-ed9df2de9807 InstallationDate: Installed on 2015-12-01 (111 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=82b73f79-8d4f-453e-b9ad-fc07955aaa21 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-34-generic N/A linux-backports-modules-4.2.0-34-generic N/A linux-firmware1.156 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd12/07/2015:svnAcer:pnAspireES1-331:pvrV1.13:rvnAcer:rnAspireES1-331:rvrV1.13:cvnAcer:ct10:cvrV1.13: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1560473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634742] Re: No button/lid events, no brightness hotkeys
Ubuntu 17.04. Brightness keys works, lid manipulations also supported properly ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634742 Title: No button/lid events, no brightness hotkeys Status in linux package in Ubuntu: Fix Released Bug description: Hardware: Acer Aspire ES1-331 with N3700 cpu. OS: Ubuntu 16.10 /proc/acpi/button/lid/LID0/state shows correct information about lid. But acpi_listen produces nothing when lid closed/open. And no output for display brightness hotkeys. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob2116 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=eb0f43dd-3aa9-49bc-88c7-de17ca52c20b InstallationDate: Installed on 2016-10-17 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0489:e095 Foxconn / Hon Hai Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-331 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=34508761-7505-4f76-909b-c0316ec558f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/20/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.16 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-331 dmi.board.vendor: Acer dmi.board.version: V1.16 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.16 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.16:bd06/20/2016:svnAcer:pnAspireES1-331:pvrV1.16:rvnAcer:rnAspireES1-331:rvrV1.16:cvnAcer:ct10:cvrV1.16: dmi.product.name: Aspire ES1-331 dmi.product.version: V1.16 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp