[Kernel-packages] [Bug 1559308] Re: Plugging HDMI screen in causes system hang
Hello, I have Linux Mint 18 with two cards: Card-1: Intel Haswell-ULT Integrated Graphics Controller Card-2: Advanced Micro Devices [AMD/ATI] Sun LE [Radeon HD 8550M / R5 As I had this issue upgrading to Kernel: 4.6.0-040600-generic x86_64 (64 bit gcc: 5.3.1) solved it. Lately I experimented some screen flickering and some tear dropping, especially when I remove the External Monitors. What Kernel should I install? Thanks Fabrizio Bertoglio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang Status in linux package in Ubuntu: Fix Released Bug description: I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1 using 4.4.0-13-generic and the Nouveau drivers. If I plug in an external HDMI monitor (FHD) either into either HDMI port (there's one on the machine and there's one available via a usb 3.1 extra adaptor) then the whole system hangs, completely unresponsive and needing a hard reboot. Before hanging the 2nd display gets an image as expected, but the laptop's screen flashes randomly, sometimes you see weird artifacts. Then the hang comes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 18 20:43:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2016-03-15 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 18 17:28:07 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5182 vendor SHP xserver.version: 2:1.18.1-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] s2lp6g003 (s390x.zKVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/s2lp6g003__4.10.0-6.8__2017-02-07_04-14-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572698] Re: Slow speed and dropped connections with Realtek RTL8192CU-based wifi
[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/1572698 Title: Slow speed and dropped connections with Realtek RTL8192CU-based wifi Status in linux package in Ubuntu: Expired Bug description: I am using a D-Link DWA-131 USB wlan adapter to connect to my private wlan. The adapter works fine under Windows and I have no problems connecting to my wlan with other devices (e.g. my laptop running Linux Mint). However, the adapter, which is based on the Realtek rtl8192cu chipset, won't work correctly on any current Ubuntu machine (in my case Kubuntu 15.10 64bit): As also showcased by a myriad of other bug reports (most of which have expired by now), wlan-adapters based on the Realtek rtl8192cu chipset exhibit very slow connection speeds and frequently dropped connections with current Linux kernels. I have noticed this originally in Linux Mint 17 running kernel 3.19.x, in Kubuntu 15.10 up to 4.2.0.35 and can confirm that it is still present in a live session of Xenial Xerus (16.04). I have tried commonly mentioned "fixes" such as deactivating hardware encryption without success. The drivers available on the Realtek homepage are apparently intended for older kernels and won't install. There is, however, a fixed driver available via github (https://github.com/pvaret/rtl8192cu-fixes). I have followed the instructions found there and finally my wlan-adapter is working correctly. Apparently the issues caused by the broken driver in the linux kernels might be connected to power management. I am posting this bug here in the hope that some developer finally manages to incorporate the (obviously available) fixes found in the github-drivers into the drivers already included in the kernel. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick2300 F pulseaudio /dev/snd/controlC1: patrick2300 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=28c49a78-8b93-495e-bc1b-22c87db4734c InstallationDate: Installed on 2015-10-22 (181 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. GA-870A-UD3 NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic root=UUID=1016b861-fa27-4990-bac9-58a3ab27ff5b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 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.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 RfKill: Tags: wily UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' Uname: Linux 4.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/01/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-870A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-870A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648640] Re: hibernate (sudo pm-hibernate) not working
[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/1648640 Title: hibernate (sudo pm-hibernate) not working Status in linux package in Ubuntu: Expired Bug description: I have 8g ram and 8g swap however sudo pm-hibernate makes the screen go off for a few seconds and then it comes back w/o restarting or halting. Everything works as normal afterwards. wifi goes off and on during the process and works normal afterwards as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-51-generic 4.4.0-51.72 ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30 Uname: Linux 4.4.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: destan 1888 F pulseaudio /dev/snd/controlC0: destan 1888 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 9 00:47:10 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-24 (228 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed root=UUID=aa1eb530-4009-4c6d-8cda-4457a3caff78 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-51-generic N/A linux-backports-modules-4.4.0-51-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B02.1503241251 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B02.1503241251:bd03/24/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] s2lp6g003 (s390x.zKVM) - tests ran: 18, failed: 0
tests ran: 18, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/s2lp6g003__4.10.0-6.8__2017-02-07_03-40-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] kernel03 (s390x.zVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/kernel03__4.10.0-6.8__2017-02-07_03-25-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1660738] s2lp6g003 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/s2lp6g003__4.10.0-6.8__2017-02-07_03-38-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1660738 Title: linux: 4.9.0-16.17 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.9.0-16.17 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1660738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642470] Re: SRU. Please re-enable CONFIG_DRM_MGAG200.
** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Critical => High ** Tags removed: somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642470 Title: SRU. Please re-enable CONFIG_DRM_MGAG200. Status in HWE Next: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in linux package in Ubuntu: Confirmed Bug description: A new Dell Precision workstation uses Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] kernel03 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/kernel03__4.10.0-6.8__2017-02-07_03-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
I've been struggling with this bug for nearly a week and only now found this issue. Thanks for fixing it! For the sake of others finding it, here's the stack trace part of the oom-killer log, which contains some terms I searched for a while ago that aren't mentioned here yet. docker invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=-1000 docker cpuset=/ mems_allowed=0 CPU: 11 PID: 4472 Comm: docker Tainted: GW 4.4.0-62-generic #83-Ubuntu Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016 0286 57f64c94 880dfb5efaf0 813f7c63 880dfb5efcc8 880fbfda 880dfb5efb60 8120ad4e 81cd2d7f 81e67760 0206 Call Trace: [] dump_stack+0x63/0x90 [] dump_header+0x5a/0x1c5 [] oom_kill_process+0x202/0x3c0 [] out_of_memory+0x219/0x460 [] __alloc_pages_slowpath.constprop.88+0x8fd/0xa70 [] __alloc_pages_nodemask+0x286/0x2a0 [] alloc_kmem_pages_node+0x4b/0xc0 [] copy_process+0x1be/0x1b70 [] ? apparmor_file_alloc_security+0x5c/0x220 [] ? kmem_cache_alloc+0x1ca/0x1f0 [] ? security_file_alloc+0x33/0x50 [] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [] _do_fork+0x80/0x360 [] SyS_clone+0x19/0x20 [] entry_SYSCALL_64_fastpath+0x16/0x71 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chas
[Kernel-packages] [Bug 1662381] 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/1662381 Title: linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: When using with dock, attached monitor is not detected, laptop monitor remains blank. Requires a reboot 4.4.0-59 works fine. I'm guessing this is due to the i915 patches for DP. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: weinberg 2945 F pulseaudio /dev/snd/controlC2: weinberg 2945 F pulseaudio /dev/snd/controlC0: weinberg 2945 F pulseaudio /dev/snd/controlC1: weinberg 2945 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 6 20:15:05 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b572432a-a870-4698-af05-eb9ac5b5dfb5 InstallationDate: Installed on 2016-05-06 (276 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1662378 Title: many OOMs on busy xenial IMAP server with lots of available memory Status in linux package in Ubuntu: Confirmed Bug description: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM- related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@grenadilla:~$ cat /proc/meminfo MemTotal: 24676320 kB MemFree: 219440 kB MemAvailable: 21593416 kB Buffers: 6186648 kB Cached: 4255608 kB SwapCached: 3732 kB Active: 7593140 kB Inactive:4404824 kB Active(anon):1319736 kB Inactive(anon): 508544 kB Active(file):6273404 kB Inactive(file): 3896280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 17912436 kB SwapFree: 17808972 kB Dirty: 524 kB Writeback: 0 kB AnonPages: 1553244 kB Mapped: 219868 kB Shmem:272576 kB Slab: 12209796 kB SReclaimable: 11572836 kB SUnreclaim: 636960 kB KernelStack: 14464 kB PageTables:54864 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:30250596 kB Committed_AS:2640808 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 18432 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 2371708 kB DirectMap2M:22784000 kB pjdc@grenadilla:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662381] [NEW] linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock
Public bug reported: When using with dock, attached monitor is not detected, laptop monitor remains blank. Requires a reboot 4.4.0-59 works fine. I'm guessing this is due to the i915 patches for DP. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: weinberg 2945 F pulseaudio /dev/snd/controlC2: weinberg 2945 F pulseaudio /dev/snd/controlC0: weinberg 2945 F pulseaudio /dev/snd/controlC1: weinberg 2945 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 6 20:15:05 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b572432a-a870-4698-af05-eb9ac5b5dfb5 InstallationDate: Installed on 2016-05-06 (276 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages 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/1662381 Title: linux-image-4.4.0-62-generic breaks Lenovo T440s on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: When using with dock, attached monitor is not detected, laptop monitor remains blank. Requires a reboot 4.4.0-59 works fine. I'm guessing this is due to the i915 patches for DP. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: weinberg 2945 F pulseaudio /dev/snd/controlC2: weinberg 2945 F pulseaudio /dev/snd/controlC0: weinberg 2945 F pulseaudio /dev/snd/controlC1: weinberg 2945 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 6 20:15:05 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b572432a-a870-4698-af05-eb9ac5b5dfb5 InstallationDate: Installed on 2016-05-06 (276 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+attachment/4814448/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662378 Title: many OOMs on busy xenial IMAP server with lots of available memory Status in linux package in Ubuntu: Confirmed Bug description: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM- related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@grenadilla:~$ cat /proc/meminfo MemTotal: 24676320 kB MemFree: 219440 kB MemAvailable: 21593416 kB Buffers: 6186648 kB Cached: 4255608 kB SwapCached: 3732 kB Active: 7593140 kB Inactive:4404824 kB Active(anon):1319736 kB Inactive(anon): 508544 kB Active(file):6273404 kB Inactive(file): 3896280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 17912436 kB SwapFree: 17808972 kB Dirty: 524 kB Writeback: 0 kB AnonPages: 1553244 kB Mapped: 219868 kB Shmem:272576 kB Slab: 12209796 kB SReclaimable: 11572836 kB SUnreclaim: 636960 kB KernelStack: 14464 kB PageTables:54864 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:30250596 kB Committed_AS:2640808 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 18432 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 2371708 kB DirectMap2M:22784000 kB pjdc@grenadilla:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662378] [NEW] many OOMs on busy xenial IMAP server with lots of available memory
Public bug reported: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM-related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@grenadilla:~$ cat /proc/meminfo MemTotal: 24676320 kB MemFree: 219440 kB MemAvailable: 21593416 kB Buffers: 6186648 kB Cached: 4255608 kB SwapCached: 3732 kB Active: 7593140 kB Inactive:4404824 kB Active(anon):1319736 kB Inactive(anon): 508544 kB Active(file):6273404 kB Inactive(file): 3896280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 17912436 kB SwapFree: 17808972 kB Dirty: 524 kB Writeback: 0 kB AnonPages: 1553244 kB Mapped: 219868 kB Shmem:272576 kB Slab: 12209796 kB SReclaimable: 11572836 kB SUnreclaim: 636960 kB KernelStack: 14464 kB PageTables:54864 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:30250596 kB Committed_AS:2640808 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 18432 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 2371708 kB DirectMap2M:22784000 kB pjdc@grenadilla:~$ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1662378/+attachment/4814447/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662378 Title: many OOMs on busy xenial IMAP server with lots of available memory Status in linux package in Ubuntu: Confirmed Bug description: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM- related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@g
[Kernel-packages] [Bug 1661741] Re: [Dell Inc. Latitude E5470] suspend/resume failure
So, a strange thing happened. In order to mitigate the problem, I decided to switch to having the computer hibernate instead of suspend (I outline below the steps I did to do that). And then, on a whim, I tried suspending again. And it stopped crashing, even after I switched back to suspend completely. I didn't do any software updates or, as far as I know, anything else in the interim. So right now, I have my computer set to suspend and it seems to work fine. I was waiting a few days to see if the problem reemered but right now, I can't reproduce it at all. For your edification (and maybe for other people), here were the steps I followed: $ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'hibernate' $ gsettings set org.gnome.settings-daemon.plugins.power \ lid-close-ac-action 'hibernate' \ && gsettings set org.gnome.settings-daemon.plugins.power \ lid-close-battery-action 'hibernate' - In /etc/systemd/logind.conf, make sure '#HandleLidSwitch=suspend' is commented out, and add HandleLidSwitch=hibernate - And then I saved the attached file to /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla To switch back, I reran the shell commands with 'suspend' instead of hibernate and then removed the changes to the config files. ** Attachment added: "com.ubuntu.enable-hibernate.pkla.disabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661741/+attachment/4814420/+files/com.ubuntu.enable-hibernate.pkla.disabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661741 Title: [Dell Inc. Latitude E5470] suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: To generate the crash: 1) Suspend the system (e.g. choose suspend from the top menu). 2) At any point, unplug the cord (the bug happens if I unplug at any point after suspend, even if I then replug before I resume) 3) Try to resume (pressing power button). Computer reboots. What should happen: Regular resume from suspend. (If I leave the computer plugged in, resume works fine.) I have performed the tests at https://wiki.ubuntu.com/DebuggingKernelSuspend and included the results. Note that the computer never crashes during any of the tests except when /sys/power/pm_test is 'none'. This appears the same/similar to #bug #1645758 but I dont't know how to add to the apport info to that bug instead of filing my own. ProblemType: KernelOops DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ganc 2892 F pulseaudio Date: Thu Dec 22 07:09:27 2016 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5470:1.11.4 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=a7e5c256-744c-41e6-823b-befb5f5c63f6 InstallationDate: Installed on 2017-01-31 (-39 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0bda:5686 Realtek Semiconductor Corp. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5470 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=1eb743a3-00e0-430e-be35-9748390e53f3 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.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux Title: [Dell Inc. Latitude E5470] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.4:bd12/22/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot
The mainline kernel seems to have resolved the issue so far. We're running some IO just to make sure it's stable. I will update the tag once we have confirmation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661131 Title: kernel crash when NVMe drive inserted in one slot Status in linux package in Ubuntu: Incomplete Bug description: Opening this on behalf of one of my colleagues at Cisco, we're seeing an issue on our new S-series S3260 server that's causing the kernel to crash. If we have an NVMe device inserted into one of two drive slots, we will see kernel crash only with Ubuntu. With an NVMe drive in the bad slot, other OS's will work fine. If we move the NVMe drive out of the bad slot and into the other slot, everything is working fine as expected. We only see the kernel crash with an NVMe drive in that bad slot when using Ubuntu. We tested with HGST and Intel NVMe drives and were able to reproduce the issue with both. HGST reviewed some logs and they don't believe at this time the issue is with the NVMe drives. We're hoping someone from Canonical can take a look to understand what is the difference between the working and failing slot. The data collection was done with the NVMe drive inserted in the working slot so we could access the OS. I had a connection time out when trying to use ubuntu-bug, so I saved the apport file and will attach to the bug. I have collected the kernel and syslog as well, but they are ~9GB. I found a call trace in the kernel log start on Jan 25 06:02:54 and floods the logs afterwards. I will include the call trace in a separate text file on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1660485] Re: Screen flicker with Intel i915 driver
** Tags added: kernel-bug-reported-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/1660485 Title: Screen flicker with Intel i915 driver Status in linux package in Ubuntu: Confirmed Bug description: After updating from 14.04 to 16.04 xenial, I am experiencing a screen flickering issue. The screen periodically completely blanks out. I tried the following kernels: 4.10.0 (daily from 1/30/2017) 4.4.0-59 (ships with 16.04) 4.1.21 (recommended from another random thread) All with the same problem. Possibly related is this error from dmesg: [5.138438] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to enable link training [5.141129] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization [5.343585] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun I also tried the following kernel options: i915_enable_fbc=0 i915_enable_rc6=0 I installed and ran the Intel graphics update tool as well. The issue occurs on a X1 Carbon (3rd gen) laptop and only with an external monitor plugged into mDisplayPort at the maximum resolution (4k). If the resolution is lowered from the max, the flickering goes away. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rvanguri 1836 F pulseaudio /dev/snd/controlC1: rvanguri 1836 F pulseaudio /dev/snd/controlC0: rvanguri 1836 F pulseaudio CurrentDesktop: XFCE Date: Mon Jan 30 18:01:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0a55c618-23a5-4af9-9a32-cf23efc5466a InstallationDate: Installed on 2017-01-21 (9 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BSCT01WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET34W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET34W(1.12):bd02/04/2016:svnLENOVO:pn20BSCT01WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCT01WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS
As of 4.10, keyboard support is in the mainline kernel, though multitouch on the touchpad is not. However, even though CONFIG_INTEL_IPTS may be there, last I checked IPTS support wasn't actually merged into mainline. Any word on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652815 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive Expected Behaviour: Pen/Touch function Actual Behaviour: Pen/Touch do not work or respond to anything Kernel/Ubuntu Versions: All Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to function. This is because touch processing is accelerated by the Intel Skylake GPU. IPTS driver can be found here: https://github.com/ipts-linux-org/ipts- linux-new/wiki Kernel compile under Debian with other Surface-specific patches can be found here: https://github.com/jimdigriz/debian-mssp4 On Reddit there are some custom kernels floating around with support patched in: https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 785668] Re: bonding inside a bridge does not update ARP correctly when bridged net accessed from within a VM
** No longer affects: qemu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/785668 Title: bonding inside a bridge does not update ARP correctly when bridged net accessed from within a VM Status in linux package in Ubuntu: Confirmed Status in qemu-kvm package in Ubuntu: Invalid Bug description: Binary package hint: qemu-kvm Description: Ubuntu 10.4.2 Release: 10.04 When setting a KVM host with a bond0 interface made of eth0 and eth1 and using this bond0 interface for a bridge to KVM VMs, the ARP tables do not get updated correctly so it is not possible for a VM to reach an IP on the bridged network up until that remote system has pinged the VM itself. Reproducible: 100%, with any of the load balancing mode How to reproduce the problem - Prerequisites: 1 One KVM system with 10.04.02 server, configured as a virtual host is needed. The following /etc/network/interfaces was used for the test : # grep -v ^# /etc/network/interfaces auto lo iface lo inet loopback auto bond0 iface bond0 inet manual post-up ifconfig $IFACE up pre-down ifconfig $IFACE down bond-slaves none bond_mode balance-rr bond-downdelay 250 bond-updelay 120 auto eth0 allow-bond0 eth0 iface eth0 inet manual bond-master bond0 auto eth1 allow-bond0 eth1 iface eth1 inet manual bond-master bond0 auto br0 iface br0 inet dhcp # dns-* options are implemented by the resolvconf package, if installed bridge-ports bond0 bridge-stp off bridge-fd 9 bridge-hello 2 bridge-maxage 12 bridge_max_wait 0 One VM running Maverick 10.10 server, standard installation, using the following /etc/network/interfaces file : grep -v ^# /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.153.107.92 netmask 255.255.255.0 network 10.153.107.0 broadcast 10.153.107.255 -- On a remote bridged network system : $ arp -an ? (10.153.107.188) à 00:1c:c4:6a:c0:dc [ether] sur tap0 ? (16.1.1.1) à 00:17:33:e9:ee:3c [ether] sur wlan0 ? (10.153.107.52) à 00:1c:c4:6a:c0:de [ether] sur tap0 On KVMhost $ arp -an ? (10.153.107.80) at ee:99:73:68:f0:a5 [ether] on br0 On VM $ arp -an ? (10.153.107.61) at on eth0 1) Test #1 : ping from VM (10.153.107.92) to remote bridged network system (10.153.107.80) : - On remote bridged network system : caribou@marvin:~$ arp -an ? (10.153.107.188) à 00:1c:c4:6a:c0:dc [ether] sur tap0 ? (16.1.1.1) à 00:17:33:e9:ee:3c [ether] sur wlan0 ? (10.153.107.52) à 00:1c:c4:6a:c0:de [ether] sur tap0 - On KVMhost ubuntu@VMhost:~$ arp -an ? (10.153.107.80) at ee:99:73:68:f0:a5 [ether] on br0 - On VM ubuntu@vm1:~$ ping 10.153.107.80 PING 10.153.107.80 (10.153.107.80) 56(84) bytes of data. From 10.153.107.92 icmp_seq=1 Destination Host Unreachable From 10.153.107.92 icmp_seq=2 Destination Host Unreachable From 10.153.107.92 icmp_seq=3 Destination Host Unreachable ^C --- 10.153.107.80 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3010ms pipe 3 ubuntu@vm1:~$ arp -an ? (10.153.107.61) at on eth0 ? (10.153.107.80) at on eth0 2) Test #2 : ping from remote bridged network system (10.153.107.80) to VM (10.153.107.92) : - On remote bridged network system : $ ping 10.153.107.92 PING 10.153.107.92 (10.153.107.92) 56(84) bytes of data. 64 bytes from 10.153.107.92: icmp_req=1 ttl=64 time=327 ms 64 bytes from 10.153.107.92: icmp_req=2 ttl=64 time=158 ms 64 bytes from 10.153.107.92: icmp_req=3 ttl=64 time=157 ms ^C --- 10.153.107.92 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 157.289/214.500/327.396/79.831 ms caribou@marvin:~$ arp -an ? (10.153.107.188) à 00:1c:c4:6a:c0:dc [ether] sur tap0 ? (16.1.1.1) à 00:17:33:e9:ee:3c [ether] sur wlan0 ? (10.153.107.52) à 00:1c:c4:6a:c0:de [ether] sur tap0 ? (10.153.107.92) à 52:54:00:8c:e0:3c [ether] sur tap0 - On KVMhost $ arp -an ? (10.153.107.80) at ee:99:73:68:f0:a5 [ether] on br0 - On VM arp -an ? (10.153.107.61) at on eth0 ? (10.153.107.80) at ee:99:73:68:f0:a5 [ether] on eth0 3) Test #3 : New ping from VM (10.153.107.92) to remote bridged network system (10.153.107.80) : - On remote bridged network system : $ arp -an ? (10.153.107.188) à 00:1c:c4:6a:c0:dc [ether] sur tap0 ? (16.1.1.1) à 00:17:33:e9:ee:3c [ether] sur wlan0 ? (10.153.107.52) à 00:1c:c4:6a:c0:de [ether] sur tap0 ? (10.153.107.92) à 52:54:00:8c:e0:3c [ether] sur tap0 - On KVMhost ubuntu@VMhost:~$ arp -an ? (10.153.107.80) at ee:99:73:68:f0:a5 [ether] on br0 - On VM ubuntu@vm1:~$ ping 10.153.107.80 PING 10.153.107.80 (10.153.107.80) 56(84) bytes of data. 64 bytes from 10.153.107.80: ic
[Kernel-packages] [Bug 1662353] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1662353 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/1662353 Title: Surface Pro 4: Mouse doesn't respond to Type keyboard Status in linux package in Ubuntu: Incomplete Bug description: While doing tests for bug 1652815 on my SP4, I noticed that if I used the mouse pad on the Type keyboard[1] - the mouse would not respond in X - if I plugged in an external mouse to the USB port - everything was fine. [1]: https://www.amazon.com/dp/B0163H1HT6/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662353] Re: Surface Pro 4: Mouse doesn't respond to Type keyboard
Using the hid_multitouch module with the kernel above. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662353 Title: Surface Pro 4: Mouse doesn't respond to Type keyboard Status in linux package in Ubuntu: New Bug description: While doing tests for bug 1652815 on my SP4, I noticed that if I used the mouse pad on the Type keyboard[1] - the mouse would not respond in X - if I plugged in an external mouse to the USB port - everything was fine. [1]: https://www.amazon.com/dp/B0163H1HT6/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662353] Re: Surface Pro 4: Mouse doesn't respond to Type keyboard
Important to note: the keyboard doesn't work at all on 16.04, it does work with the linux-surface kernel in the https://launchpad.net/~tigerite/+archive/ubuntu/kernel PPA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662353 Title: Surface Pro 4: Mouse doesn't respond to Type keyboard Status in linux package in Ubuntu: New Bug description: While doing tests for bug 1652815 on my SP4, I noticed that if I used the mouse pad on the Type keyboard[1] - the mouse would not respond in X - if I plugged in an external mouse to the USB port - everything was fine. [1]: https://www.amazon.com/dp/B0163H1HT6/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS
I think a good start here would be to set CONFIG_INTEL_IPTS=m in the kernel config. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652815 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive Expected Behaviour: Pen/Touch function Actual Behaviour: Pen/Touch do not work or respond to anything Kernel/Ubuntu Versions: All Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to function. This is because touch processing is accelerated by the Intel Skylake GPU. IPTS driver can be found here: https://github.com/ipts-linux-org/ipts- linux-new/wiki Kernel compile under Debian with other Surface-specific patches can be found here: https://github.com/jimdigriz/debian-mssp4 On Reddit there are some custom kernels floating around with support patched in: https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS
Joe, I don't think Ubuntu's ever worked withe SP4; people need to use the special kernel from this PPA for the detachable keyboard to work: https://launchpad.net/~tigerite/+archive/ubuntu/kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652815 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive Expected Behaviour: Pen/Touch function Actual Behaviour: Pen/Touch do not work or respond to anything Kernel/Ubuntu Versions: All Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to function. This is because touch processing is accelerated by the Intel Skylake GPU. IPTS driver can be found here: https://github.com/ipts-linux-org/ipts- linux-new/wiki Kernel compile under Debian with other Surface-specific patches can be found here: https://github.com/jimdigriz/debian-mssp4 On Reddit there are some custom kernels floating around with support patched in: https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652815] Re: Surface Pro 4 Touch/Pen requires IPTS
Tested with 4.10.0-041000rc7-generic on 16.04 LTS - I do not have touchscreen capabilities on my Surface Pro 4. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream ** Tags added: kernel-bug-exists-upstream-4.10-rc7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652815 Title: Surface Pro 4 Touch/Pen requires IPTS Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive Expected Behaviour: Pen/Touch function Actual Behaviour: Pen/Touch do not work or respond to anything Kernel/Ubuntu Versions: All Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to function. This is because touch processing is accelerated by the Intel Skylake GPU. IPTS driver can be found here: https://github.com/ipts-linux-org/ipts- linux-new/wiki Kernel compile under Debian with other Surface-specific patches can be found here: https://github.com/jimdigriz/debian-mssp4 On Reddit there are some custom kernels floating around with support patched in: https://www.reddit.com/r/SurfaceLinux/comments/4t64zt/getting_the_sp4_running_with_ubuntu_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662353] [NEW] Surface Pro 4: Mouse doesn't respond to Type keyboard
Public bug reported: While doing tests for bug 1652815 on my SP4, I noticed that if I used the mouse pad on the Type keyboard[1] - the mouse would not respond in X - if I plugged in an external mouse to the USB port - everything was fine. [1]: https://www.amazon.com/dp/B0163H1HT6/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.10-rc7 ** Summary changed: - Surface Pro 4: Mouse disappears using Type keyboard + Surface Pro 4: Mouse doesn't respond to Type keyboard ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.10-rc7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662353 Title: Surface Pro 4: Mouse doesn't respond to Type keyboard Status in linux package in Ubuntu: New Bug description: While doing tests for bug 1652815 on my SP4, I noticed that if I used the mouse pad on the Type keyboard[1] - the mouse would not respond in X - if I plugged in an external mouse to the USB port - everything was fine. [1]: https://www.amazon.com/dp/B0163H1HT6/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Note, the above comment was validated on a Fujitsu CX1640 Xeon Phi system with Xenial and the stock ubuntu kernel: Linux cx1640-1 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
FWIW, I have run this on a Xeon Phi system and not reproduced the failure using stress-ng 0.07.16 (built in our PPA for Xenial). This appears to have an AMI fake keyboard and mouse as the Power system that fails does. Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x046b American Megatrends, Inc. idProduct 0xff10 Virtual Keyboard and Mouse bcdDevice1.00 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 3 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 4 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 63 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 and ubuntu@cx1640-1:~$ lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 003 Device 002: ID 05af:1012 Jing-Mold Enterprise Co., Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub This appears to be the same virtual HID device that the failing power system has. Though as this is a Xeon Phi system, not an OpenPower box, do not treat this as conclusive that the bug is fixed for the failing system. The summary says to run fstat 10 times, so I ran it in a loop like so and did not experience any lockups: for x in `seq 1 10`; do sudo stress-ng --fstat 128 -t 60 -v; done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpowe
[Kernel-packages] [Bug 1662316] Re: Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662316 Title: Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working Status in linux package in Ubuntu: Triaged Bug description: There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight 1) Keyboard backlight uncontrollable 2) Most FN keys don't work There is no way to control keyboard backlight at all (already tried all possible ways found in internet) Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed) try all possible variants with acpi_osi and acpi_backlight from forum - no effect. Install kernel 4.9 and even 4.10 latest RC - no effect (only got control over airplane led). Keyboard backlight is always on or always off (last state from windows) Fn keys not working: F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable) Workjng: Sound Mute + - (F10 F11 F12) Monitor backlight working fine by using menu slider. Tested on open and proprietary drivers from latest ppas lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Suggestion: asus-nb-wmi kernel module unable to detect hardware ProblemType: Bug 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cabalbl4 1713 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 6 23:18:11 2017 HibernationDevice: RESUME=UUID=6ab6365a-c88a-4e64-a529-83b6a9a70e4e InstallationDate: Installed on 2017-02-05 (1 days ago) InstallationMedia: Kubuntu 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:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=18b6e8b1-63c2-4fb9-bdbb-5f9ffcc2d4cf ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VE.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VE.208:bd11/08/2016:svnASUSTeKCOMPUTERINC.:pnGL553VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VE 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/1662316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662316] 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/1662316 Title: Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working Status in linux package in Ubuntu: Confirmed Bug description: There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight 1) Keyboard backlight uncontrollable 2) Most FN keys don't work There is no way to control keyboard backlight at all (already tried all possible ways found in internet) Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed) try all possible variants with acpi_osi and acpi_backlight from forum - no effect. Install kernel 4.9 and even 4.10 latest RC - no effect (only got control over airplane led). Keyboard backlight is always on or always off (last state from windows) Fn keys not working: F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable) Workjng: Sound Mute + - (F10 F11 F12) Monitor backlight working fine by using menu slider. Tested on open and proprietary drivers from latest ppas lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Suggestion: asus-nb-wmi kernel module unable to detect hardware ProblemType: Bug 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cabalbl4 1713 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 6 23:18:11 2017 HibernationDevice: RESUME=UUID=6ab6365a-c88a-4e64-a529-83b6a9a70e4e InstallationDate: Installed on 2017-02-05 (1 days ago) InstallationMedia: Kubuntu 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:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=18b6e8b1-63c2-4fb9-bdbb-5f9ffcc2d4cf ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VE.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VE.208:bd11/08/2016:svnASUSTeKCOMPUTERINC.:pnGL553VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VE 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/1662316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
Thanks for the reply. Since I have had some additional time on my hand I have played around a bit with kernels and firmwares. Currently I do not think this is a upstream bug since I can get the laptop and it's NVME devices etc. to work properly using the latest Solus Linux version and that is running Kernel 4.9.6. I did try to use the same kernel with Ubuntu 16.10 and the 17.04 ALPHA builds, but I was not able to get the suspend to work with my NVME devices and WiFi. I suspect that the linux firmware might be what is different here, but can't say for sure since I'm far from an expert on how the Linux kernel should operate with these new kinds of devices. Hopefully this additional information might be of use for 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/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- 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.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662316] [NEW] Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working
Public bug reported: There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight 1) Keyboard backlight uncontrollable 2) Most FN keys don't work There is no way to control keyboard backlight at all (already tried all possible ways found in internet) Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed) try all possible variants with acpi_osi and acpi_backlight from forum - no effect. Install kernel 4.9 and even 4.10 latest RC - no effect (only got control over airplane led). Keyboard backlight is always on or always off (last state from windows) Fn keys not working: F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable) Workjng: Sound Mute + - (F10 F11 F12) Monitor backlight working fine by using menu slider. Tested on open and proprietary drivers from latest ppas lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Suggestion: asus-nb-wmi kernel module unable to detect hardware ProblemType: Bug 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cabalbl4 1713 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 6 23:18:11 2017 HibernationDevice: RESUME=UUID=6ab6365a-c88a-4e64-a529-83b6a9a70e4e InstallationDate: Installed on 2017-02-05 (1 days ago) InstallationMedia: Kubuntu 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:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=18b6e8b1-63c2-4fb9-bdbb-5f9ffcc2d4cf ro quiet splash acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VE.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VE.208:bd11/08/2016:svnASUSTeKCOMPUTERINC.:pnGL553VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL553VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug asus asus-nb-wmi xenial ** Description changed: There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight 1) Keyboard backlight uncontrollable 2) Most FN keys don't work There is no way to control keyboard backlight at all (already tried all possible ways found in internet) Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed) try all possible variants with acpi_osi and acpi_backlight from forum - no effect. Install kernel 4.9 and even 4.10 latest RC - no effect (only got control over airplane led). Keyboard backlight is always on or always off (last state from windows) - Fn keys not working: - F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) F5(Brightness up) F6(Brightness down) F7(Screen dim) F9(Touchpad disable) + Fn keys not working: + F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable) Workjng: Sound Mute + - (F10 F11 F12) Monitor backlight working fine by using menu slider. Tested on open and proprietary drivers from latest ppas lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 Suggestion: asus-nb-wmi kernel module unable to detect hardware ProblemType: Bug 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 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: cabalbl4 1713 F pulseaudio + USERPID AC
[Kernel-packages] [Bug 1661695] Re: screen flickering raedon
similar bug with the same card https://bugs.freedesktop.org/show_bug.cgi?id=73116 By the way, I tried using amdgpu driver by compiling a daily kernel using Enable amdgpu support for SI/CIK parts and blacklisting radeon and the issue still exists with the amdgpu driver as well. ** Bug watch added: freedesktop.org Bugzilla #73116 https://bugs.freedesktop.org/show_bug.cgi?id=73116 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661695 Title: screen flickering raedon Status in linux package in Ubuntu: Incomplete Bug description: 4.4.0-53 WORKS FINE 4.4.0-62 DOES NOT WORK (screen flickers) It seems there is a problem with powersafe: With auto: echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level you will see heavy screen flickering on higher display resolutions With low or high: echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level there is no screen flickering And having performance level set to HIGH at all times is not a workaround because it wears out the card. :( details: Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ``` Vendor: X.Org (0x1002) Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811) Version: 17.1.0 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.2 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - padoka PPA OpenGL core profile shading language version string: 4.20 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile ``` --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: atomi 3734 F pulseaudio /dev/snd/controlC0: atomi 3734 F pulseaudio /dev/snd/controlC1: atomi 3734 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b InstallationDate: Installed on 2016-12-27 (37 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 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 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: serena Uname: Linux 4.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659623] Re: Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+
Would it be possible for you to test this latest kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659623 Title: Shutdown/reboot hang on Dell XPS 15 9550 BIOS 1.2.18+ Status in linux package in Ubuntu: Incomplete Bug description: On Dell XPS 15 9550 BIOS 1.2.18+, shutdown/reboot job is delayed for several seconds in Ubuntu kernel. After shutdown screen appears and all shutdown sequence had been done, the power LED turns off; however the front LED is flashing in orange for several seconds and the system finally turns off. Rebooting is also not working: front LED flashes in orange and the system just turns off. Switching to mainline kernel 4.9.6, or downgrading to BIOS 1.2.16 solved the problem. Other Linux distro users didn't observed the problem, see also: * https://www.reddit.com/r/Dell/comments/5przxq/new_dell_xps_15_9550_bios_1219/ * https://www.reddit.com/r/Dell/comments/5l9n3b/xps_15_9550_bios_1218_ubuntu_1610_shutdown_problem/ ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psj5638 F pulseaudio CurrentDesktop: KDE Date: Thu Jan 26 19:17:24 2017 HibernationDevice: RESUME=UUID=2cfb78ae-e2b8-4d3a-9ab2-a61ae1a79fd1 InstallationDate: Installed on 2016-01-21 (371 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=db90ced3-4cfe-4001-b877-d4aa35e7260f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-14 (103 days ago) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.19 dmi.board.asset.tag: ainazi dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: ainazi dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.19:bd12/22/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/1659623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1660485] Re: Screen flicker with Intel i915 driver
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1660485 Title: Screen flicker with Intel i915 driver Status in linux package in Ubuntu: Confirmed Bug description: After updating from 14.04 to 16.04 xenial, I am experiencing a screen flickering issue. The screen periodically completely blanks out. I tried the following kernels: 4.10.0 (daily from 1/30/2017) 4.4.0-59 (ships with 16.04) 4.1.21 (recommended from another random thread) All with the same problem. Possibly related is this error from dmesg: [5.138438] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to enable link training [5.141129] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization [5.343585] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun I also tried the following kernel options: i915_enable_fbc=0 i915_enable_rc6=0 I installed and ran the Intel graphics update tool as well. The issue occurs on a X1 Carbon (3rd gen) laptop and only with an external monitor plugged into mDisplayPort at the maximum resolution (4k). If the resolution is lowered from the max, the flickering goes away. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rvanguri 1836 F pulseaudio /dev/snd/controlC1: rvanguri 1836 F pulseaudio /dev/snd/controlC0: rvanguri 1836 F pulseaudio CurrentDesktop: XFCE Date: Mon Jan 30 18:01:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0a55c618-23a5-4af9-9a32-cf23efc5466a InstallationDate: Installed on 2017-01-21 (9 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BSCT01WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET34W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET34W(1.12):bd02/04/2016:svnLENOVO:pn20BSCT01WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCT01WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661695] Re: screen flickering raedon
** Description changed: 4.4.0-53 WORKS FINE 4.4.0-62 DOES NOT WORK (screen flickers) It seems there is a problem with powersafe: With auto: echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level you will see heavy screen flickering on higher display resolutions With low or high: echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level there is no screen flickering And having performance level set to HIGH at all times is not a workaround because it wears out the card. :( details: Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux - ``` - Vendor: X.Org (0x1002) - Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811) - Version: 17.1.0 - Accelerated: yes - Video memory: 2048MB - Unified memory: no - Preferred profile: core (0x1) - Max core profile version: 4.2 - Max compat profile version: 3.0 - Max GLES1 profile version: 1.1 - Max GLES[23] profile version: 3.0 + Vendor: X.Org (0x1002) + Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811) + Version: 17.1.0 + Accelerated: yes + Video memory: 2048MB + Unified memory: no + Preferred profile: core (0x1) + Max core profile version: 4.2 + Max compat profile version: 3.0 + Max GLES1 profile version: 1.1 + Max GLES[23] profile version: 3.0 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - padoka PPA OpenGL core profile shading language version string: 4.20 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile ``` - --- + --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: atomi 3734 F pulseaudio - /dev/snd/controlC0: atomi 3734 F pulseaudio - /dev/snd/controlC1: atomi 3734 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: atomi 3734 F pulseaudio + /dev/snd/controlC0: atomi 3734 F pulseaudio + /dev/snd/controlC1: atomi 3734 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b InstallationDate: Installed on 2016-12-27 (37 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 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 + linux-restricted-modules-4.4.0-53-generic N/A + linux-backports-modules-4.4.0-53-generic N/A + linux-firmware1.157.6 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no Tags: serena Uname: Linux 4.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/1661695 Title: screen flickering raedon Status in linux package in Ubuntu: Incomplete Bug description: 4.4.0-53 WORKS FINE 4.4.0-62 DOES NOT WORK (screen flickers) It seems there is a problem with powersafe: With auto: echo auto > /sys/class/drm/card0/device/powe
[Kernel-packages] [Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- 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.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659750] Re: Wifi does not work
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Triaged Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 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: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661525] Re: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation
As suggested ran: sudo apt-get install -f sudo apt-get clean sudo apt-get update and ran updater - no error. So fixed for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661525 Title: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.10 Release: 16.10 I ran the software updater, clicked to install then errors came up - see summary. Tried to fix using Synaptic but similar result. The file /lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new does not exist but zfs.ko does. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: campbell 4954 F pulseaudio /dev/snd/controlC1: campbell 4954 F pulseaudio Date: Thu Feb 2 22:29:56 2017 DpkgTerminalLog: Preparing to unpack .../0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb ... Done. Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-O24Y4E/0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb (--unpack): unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted DuplicateSignature: package:linux-image-4.8.0-37-generic:4.8.0-37.39 Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-O24Y4E/0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb (--unpack): unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (870 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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~beta2-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662017] Re: package linux-image-4.4.0-62-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662017 Title: package linux-image-4.4.0-62-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: Incomplete Bug description: I have old Computer and i did "force pae" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 2704 F pulseaudio Date: Sun Feb 5 22:51:50 2017 DuplicateSignature: package:linux-image-4.4.0-62-generic:(not installed) Preparing to unpack .../linux-image-4.4.0-62-generic_4.4.0-62.83_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-62-generic_4.4.0-62.83_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=2630dd91-80d2-4534-8aa6-7aceb5b68324 InstallationDate: Installed on 2017-02-05 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 2373F3G 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-31-generic root=UUID=7807ee7c-d7fa-4b6f-86ec-06250866f088 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~beta2-36ubuntu3.7 SourcePackage: linux Title: package linux-image-4.4.0-62-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373F3G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373F3G:pvrThinkPadT42:rvnIBM:rn2373F3G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373F3G dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659231] Re: drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) for Kernel > 4.6
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659231 Title: drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) for Kernel > 4.6 Status in linux package in Ubuntu: Incomplete Bug description: After upgrading driver from 2:2.99.917+git20160325-1ubuntu1 to 2:2.99.917+git20160706-1ubuntu1, Whenever I open ¨Unity-Control-Center¨ makes the system unresponsive for a while and sometimes forever. Same thing happens if I try to open power or sound settings from indicators or when I try to add online accounts in evolution. I can reproduce same with totem. But all other applications are working fine. And everything works in Yakkety. Screencast:https://youtu.be/69PJZf055V8 I am happy to provide any other debugging info. Just don ask to use ¨apport collect¨ as it hangs as well! I can provide details manually through syslog or something. System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960 Integrated Graphics) Graphics driver: i915 Os: Ubuntu 17.04, 32bit UCC: 15.04.0+17.04.20161125.1-0ubuntu1 Edit: If I boot to recovery and use gallium 0.4 on llvmpipe, problem disappears as well. That is why I think itś some sort of graphics issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662078] Re: System halts during shut down and hibernate
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.10 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.10-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/1662078 Title: System halts during shut down and hibernate Status in linux package in Ubuntu: Incomplete Bug description: The system completely halts while trying to shut down or hibernate. Restart works fine. Tried Ubuntu/lubuntu on different laptop (Acer ES1 533-P4PA) on every system it is having the same problem. The version I am using is : Description:Ubuntu 16.10 Release:16.10 I tried several methods like changing the acpi as provided in the form, but none seems to work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-37-generic. ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ll-l2 1463 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9131 irq 205' Mixer name : 'Realtek ALC233' Components : 'HDA:10ec0235,10251084,0012 HDA:8086280a,80860101,0010' Controls : 42 Simple ctrls : 13 Date: Mon Feb 6 10:53:50 2017 HibernationDevice: RESUME=UUID=79497307-14e3-4a30-aecc-1efe0b8165d0 InstallationDate: Installed on 2017-02-03 (2 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b3 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-533 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=90b5ad8e-c7be-433d-9991-fe323bb881fa ro quiet splash vt.handoff=7 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-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stego_AP dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd09/07/2016:svnAcer:pnAspireES1-533:pvrV1.04:rvnAcer:rnStego_AP:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.name: Aspire ES1-533 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661941] Re: cant connect to wifi
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.10 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.10-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661941 Title: cant connect to wifi Status in linux package in Ubuntu: Incomplete Bug description: i am not able to connect to wifi. there is no enable wifi option in network menu. how can i solve this issue ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-108-generic 3.13.0-108.155 ProcVersionSignature: Ubuntu 3.13.0-108.155-generic 3.13.11-ckt39 Uname: Linux 3.13.0-108-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vaishu 1624 F pulseaudio /dev/snd/controlC0: vaishu 1624 F pulseaudio CurrentDesktop: Unity Date: Sun Feb 5 15:14:16 2017 HibernationDevice: RESUME=UUID=c2875e73-69d3-4af6-a684-4549c277bfdd InstallationDate: Installed on 2015-08-25 (530 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:930b Suyin Corp. Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-108-generic.efi.signed root=UUID=9908fc28-804a-4434-bebe-3936e27dfd42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-108-generic N/A linux-backports-modules-3.13.0-108-generic N/A linux-firmware 1.127.23 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2017-01-09 (26 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.47 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.21:bd05/17/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.47:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 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/1661941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661901] Re: Laptop suspended while connected to TV via HDMI and backlight went out
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.10 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.10-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/1661901 Title: Laptop suspended while connected to TV via HDMI and backlight went out Status in linux package in Ubuntu: Incomplete Bug description: Backlight now non functional even when rebooting. No backlight in bios screen or when OS boots ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: doc7697 F...m pulseaudio /dev/snd/controlC0: doc7697 F pulseaudio CurrentDesktop: XFCE Date: Sun Feb 5 00:54:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3baeb745-d8b3-48bb-ab61-e6104afb4154 InstallationDate: Installed on 2017-01-06 (29 days ago) InstallationMedia: Xubuntu 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 003: ID 04f2:b52d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash acpi_backlight=vendor acpi_osi=Linux video.use_native_backlight=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.30 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.14:bd08/01/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.30:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx
Perfect, thank you very much - this did the trick, for me too. -- 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/1654708 Title: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/ Status in zfs-linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 zfs-dkms 0.6.5.6-0ubuntu15 I cant mount/install my zpool. so i tried reinstalling zfslinux-utils, which gives me three error messages like this: "zfs-mount.service is a disabled" or a static unit, not starting it."... If something doesn't work I try googling error messages. most answers not totally like my problem but related to dkms, so I tried loading zfs-dkms and reinstalling zfslinux-utils. I created the zpool with id from /mnt/disk/by-id/ - which is zfs good- practice. This may be causing problems with the mount. I dont know... Cheers. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu15 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 DKMSKernelVersion: 4.4.0-58-generic Date: Sat Jan 7 15:58:15 2017 DuplicateSignature: dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12: error: too few arguments to function ‘posix_acl_valid’ InstallationDate: Installed on 2016-12-26 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225) PackageVersion: 0.6.5.6-0ubuntu15 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1654708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661916] Re: package linux-headers-generic 3.13.0.86.92 failed to install/upgrade: subprocess dpkg-deb --control was killed by signal (Killed)
** 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/1661916 Title: package linux-headers-generic 3.13.0.86.92 failed to install/upgrade: subprocess dpkg-deb --control was killed by signal (Killed) Status in linux package in Ubuntu: Incomplete Bug description: Attempting do-release-upgrade A previous kernel package install (version ~3.13) was in an Reinstall state; so I reinstalled and then purged it, using dpkg. System was tested before do-release-upgrade, by rebooting, and checking kernel version (version 4.4...). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-generic 3.13.0.86.92 ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 5 14:40 seq crw-rw 1 root audio 116, 33 Feb 5 14:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Feb 5 15:33:38 2017 DuplicateSignature: package:linux-headers-generic:3.13.0.86.92 Unpacking linux-headers-4.4.0-62-generic (4.4.0-62.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-generic_4.4.0.62.65_amd64.deb (--unpack): subprocess dpkg-deb --control was killed by signal (Killed) ErrorMessage: subprocess dpkg-deb --control was killed by signal (Killed) HibernationDevice: RESUME=UUID=0d5aa5d4-df45-4974-b4aa-075577998c2c InstallationDate: Installed on 2013-06-24 (1321 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IwConfig: tun0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=970ddf7f-22d6-4a36-9c36-eec6134f02a2 ro RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux Title: package linux-headers-generic 3.13.0.86.92 failed to install/upgrade: subprocess dpkg-deb --control was killed by signal (Killed) UpgradeStatus: Upgraded to xenial on 2017-02-05 (0 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661782] Re: No mouse and/or wifi with latest kernel
I'll mark the bug as incomplete for now, since you no longer see it. Just change the status back to confirmed if the bug returns. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Yakkety) 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/1661782 Title: No mouse and/or wifi with latest kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After upgrading to linux-image-4.8.0-37-generic, bootup suddenly takes much longer than with previous kernels (minutes vs 14 seconds or so), usually the mouse (built in trackpad) doesn't do anything and cursor pointer isn't there, and wifi doesn't work either. On one occasion, both of those worked and everything worked correctly. One other instance had just the mouse/cursor, but no wifi. All other times, neither of the two were present. Booting up the previous kernel (4.8.0-34.36) makes everything work properly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philb 2775 F pulseaudio /dev/snd/pcmC1D0p: philb 2775 F...m pulseaudio /dev/snd/controlC1: philb 2775 F pulseaudio CurrentDesktop: Unity Date: Fri Feb 3 16:19:22 2017 HibernationDevice: RESUME=UUID=b4ef2eb3-4df9-46c8-84ff-0401a111b715 InstallationDate: Installed on 2015-07-06 (578 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=222170f0-c6c8-4417-adbb-2ce31a617aac ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-16 (110 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661878] Re: [Asus UX360UA] Physical screen rotation is not detected
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.10 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.10-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/1661878 Title: [Asus UX360UA] Physical screen rotation is not detected Status in linux package in Ubuntu: Incomplete Bug description: I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. This laptop has a 360º degree rotating screen. When I physically rotate my screen, Windows (or some installed driver, I don't know) detects that. Consequently, the image being displayed in the screen is rotated 180º and the keyboard is blocked. However, Ubuntu doesn't do nothing when I rotate the screen. I think this is a bug because a fresh Ubuntu installation should recognise these laptop features. I searched a little bit and it seems there are some workarounds on this, but I guess Ubuntu installation should recognise this automatically? --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
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.10 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.10-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/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Incomplete Bug description: I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661864] Re: [Asus UX360UA] Some Keyboard and hardware not recognised automatically
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.10 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.10-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/1661864 Title: [Asus UX360UA] Some Keyboard and hardware not recognised automatically Status in linux package in Ubuntu: Incomplete Bug description: I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. The following sequence of keys are not working: FN+F2 (activate flight mode?) - I think in a way it stops my internet connection but I don't see any visual feedback on the screen nor the light in the "F2" key is turned on/off FN+F5 / FN+F6 (adjust brightness) FN+F7 (turn off screen) Also, the hardware buttons on left side of the laptop for changing the volume are not working. I click on them and the volume keeps the same --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1895 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662187] Re: apt-get upgrade hung when it comes to update initramfs
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662187 Title: apt-get upgrade hung when it comes to update initramfs Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1662187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661394] Re: Asus X206H Bluetooth / WLAN Malfunktion
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.10 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.10-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/1661394 Title: Asus X206H Bluetooth / WLAN Malfunktion Status in linux package in Ubuntu: Incomplete Bug description: Hi There, got a unpleasant bug in (K)ubuntu 16.10 which wont establish a connection simultaneously with bluetooth and WLAN. If Bluetooth is established, WLAN connection gets down to 0 Bytes, but seems to stay connected. The same goes via Bluetooth. The Both work just a few seconds at the same time, then one of them gets "offline", but stay connected. I tested that with Bluetooth Earplugs, and the connection seems to go bad in form of noisy sound, in that time WLAN is continuously working until it goes down to 0 Bytes. Kernel Version is: Ubuntu 4.8.0-34.36-generic 4.8.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661525] Re: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** 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/1661525 Title: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.10 Release: 16.10 I ran the software updater, clicked to install then errors came up - see summary. Tried to fix using Synaptic but similar result. The file /lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new does not exist but zfs.ko does. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: campbell 4954 F pulseaudio /dev/snd/controlC1: campbell 4954 F pulseaudio Date: Thu Feb 2 22:29:56 2017 DpkgTerminalLog: Preparing to unpack .../0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb ... Done. Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-O24Y4E/0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb (--unpack): unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted DuplicateSignature: package:linux-image-4.8.0-37-generic:4.8.0-37.39 Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-O24Y4E/0-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb (--unpack): unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=b7290e2f-642a-414d-988b-cac7bac6530e InstallationDate: Installed on 2014-09-17 (870 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic root=UUID=fc6ea265-b75c-458a-b5d2-2950ebad0828 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~beta2-36ubuntu11 RfKill: SourcePackage: linux Title: package linux-image-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to open '/lib/modules/4.8.0-37-generic/kernel/zfs/zfs/zfs.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661462] Re: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.l
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** 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/1661462 Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- image-extra-4.8.0-37-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: not a tech guy but trying to do my part hope it helps. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-extra-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apollo30 3426 F pulseaudio Date: Thu Feb 2 19:34:49 2017 DuplicateSignature: package:linux-image-extra-4.8.0-37-generic:4.8.0-37.39 Unpacking linux-image-4.8.0-37-generic (4.8.0-37.39) ... dpkg: error processing archive /tmp/apt-dpkg-install-PWl0Ok/03-linux-image-4.8.0-37-generic_4.8.0-37.39_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-image-4.8.0-37-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not permitted HibernationDevice: RESUME=UUID=a0124356-9144-4037-adc9-975b85afab53 InstallationDate: Installed on 2016-08-31 (155 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-37-generic root=/dev/mapper/ubuntu--vg-root 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-36ubuntu11 SourcePackage: linux Title: package linux-image-extra-4.8.0-37-generic 4.8.0-37.39 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.8.0-37-generic.list-new': Operation not permitted UpgradeStatus: Upgraded to yakkety on 2017-01-05 (28 days ago) dmi.bios.date: 05/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.0A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0A:bd05/02/2012:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr07901020571620100:rvnHewlett-Packard:rn181D:rvr52.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 07901020571620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661475] Re: i915 driver fails to resume display from suspend
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-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/1661475 Title: i915 driver fails to resume display from suspend Status in linux package in Ubuntu: Incomplete Bug description: Symptom is that the LCD on the laptop (Dell Latitude E7450) stays off after boot. The laptop is running fine and can be reached via SSH, and rebooted. I can also kill the Xorg server at which point my display manager starts a new session and restores the driver. I believe the display driver is failing to resume as indicated by this kernel log line: Feb 2 19:08:33 LON-IX-L-763 kernel: [32839.947460] [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22 This looks like a regression in a recent kernel; this worked fine for ~1 year on Ubuntu 15.10 but I didn't test it on 16.04 so I can't confirm if it exists there. I suspend the machine by running pm-suspend, and it is resumed by the lid open event. I've attached the relevant time from /var/log/syslog which shows the kernel messages; this suspend was entered at 18:16:30 and woken up at 19:08:33. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-extra-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: pv 4009 F...m pulseaudio /dev/snd/controlC1: pv 4009 F pulseaudio /dev/snd/controlC0: pv 4009 F pulseaudio /dev/snd/seq:pv 4126 F chrome Date: Fri Feb 3 03:23:55 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=adb71bac-b2c6-4c48-9f39-8b07f2b1d7b7 InstallationDate: Installed on 2015-07-24 (559 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=3cd0b0b6-f38d-45bf-85aa-e6578b5e37c4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-12-19 (45 days ago) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0R1VJD dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661695] Re: screen flickering raedon
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1661695 Title: screen flickering raedon Status in linux package in Ubuntu: Incomplete Bug description: 4.4.0-53 WORKS FINE 4.4.0-62 DOES NOT WORK (screen flickers) It seems there is a problem with powersafe: With auto: echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level you will see heavy screen flickering on higher display resolutions With low or high: echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level there is no screen flickering And having performance level set to HIGH at all times is not a workaround because it wears out the card. :( details: Linux CINNAMON 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ``` Vendor: X.Org (0x1002) Device: AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) (0x6811) Version: 17.1.0 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.2 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0 / 4.4.0-62-generic, LLVM 5.0.0) OpenGL core profile version string: 4.2 (Core Profile) Mesa 17.1.0-devel - padoka PPA OpenGL core profile shading language version string: 4.20 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile ``` --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: atomi 3734 F pulseaudio /dev/snd/controlC0: atomi 3734 F pulseaudio /dev/snd/controlC1: atomi 3734 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=30254b0c-14d7-4c0e-9168-a8d492fa027b InstallationDate: Installed on 2016-12-27 (37 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=41cc7dce-52e8-4b29-9347-60afc0a7d0ed ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 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 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: serena Uname: Linux 4.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661741] Re: [Dell Inc. Latitude E5470] suspend/resume failure
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.10 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.10-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1661741 Title: [Dell Inc. Latitude E5470] suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: To generate the crash: 1) Suspend the system (e.g. choose suspend from the top menu). 2) At any point, unplug the cord (the bug happens if I unplug at any point after suspend, even if I then replug before I resume) 3) Try to resume (pressing power button). Computer reboots. What should happen: Regular resume from suspend. (If I leave the computer plugged in, resume works fine.) I have performed the tests at https://wiki.ubuntu.com/DebuggingKernelSuspend and included the results. Note that the computer never crashes during any of the tests except when /sys/power/pm_test is 'none'. This appears the same/similar to #bug #1645758 but I dont't know how to add to the apport info to that bug instead of filing my own. ProblemType: KernelOops DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ganc 2892 F pulseaudio Date: Thu Dec 22 07:09:27 2016 DuplicateSignature: suspend/resume:Dell Inc. Latitude E5470:1.11.4 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=a7e5c256-744c-41e6-823b-befb5f5c63f6 InstallationDate: Installed on 2017-01-31 (-39 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0bda:5686 Realtek Semiconductor Corp. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5470 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=1eb743a3-00e0-430e-be35-9748390e53f3 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.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 SourcePackage: linux Title: [Dell Inc. Latitude E5470] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.4:bd12/22/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx
Some more details A posix function in kernel has changed between 4.4.0-57 and 4.4.0-59 ./linux-headers-4.4.0-53/include/linux/posix_acl.h:extern int posix_acl_valid(const struct posix_acl *); ./linux-headers-4.4.0-57/include/linux/posix_acl.h:extern int posix_acl_valid(const struct posix_acl *); ./linux-headers-4.4.0-59/include/linux/posix_acl.h:extern int posix_acl_valid(struct user_namespace *, const struct posix_acl *); ./linux-headers-4.4.0-62/include/linux/posix_acl.h:extern int posix_acl_valid(struct user_namespace *, const struct posix_acl *); The zfs kernel modul is not updated to match these changes. see: https://fossies.org/diffs/zfs/0.6.5.7_vs_0.6.5.8/module/zfs/zpl_xattr.c-diff.html I have tried the following: Replaced all occurrences error = posix_acl_valid(acl); with error = posix_acl_valid(ip, acl); in file: /usr/src/zfs-0.6.5.6/module/zfs/zpl_xattr.c dkms remove -m zfs -v 0.6.5.6 -k 4.4.0-62-generic dkms install --force -m zfs -v 0.6.5.6 -k 4.4.0-62-generic does compiles now. System seems to work. -- 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/1654708 Title: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/ Status in zfs-linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 zfs-dkms 0.6.5.6-0ubuntu15 I cant mount/install my zpool. so i tried reinstalling zfslinux-utils, which gives me three error messages like this: "zfs-mount.service is a disabled" or a static unit, not starting it."... If something doesn't work I try googling error messages. most answers not totally like my problem but related to dkms, so I tried loading zfs-dkms and reinstalling zfslinux-utils. I created the zpool with id from /mnt/disk/by-id/ - which is zfs good- practice. This may be causing problems with the mount. I dont know... Cheers. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu15 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 DKMSKernelVersion: 4.4.0-58-generic Date: Sat Jan 7 15:58:15 2017 DuplicateSignature: dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12: error: too few arguments to function ‘posix_acl_valid’ InstallationDate: Installed on 2016-12-26 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225) PackageVersion: 0.6.5.6-0ubuntu15 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1654708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1505178] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2017-02-06 12:36 EDT--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1505178 Title: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 == When running STX on Habanero systems with PMC Sierra, the following linux error messages are found when running "dmesg -T --level=alert,crit,err" after the run. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18177 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18181 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18185 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18189 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18194 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18200 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18205 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18213 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18221 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. We are running the following code levels. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 14.04.3 LTS \n \l Kernel Version: 3.19.0-25-generic HTX Version: htxubuntu-357 Host Name: rcx2c357 Machine Serial No: 1035C5A Machine Type/Model: 8348-21C We have a very limited number of PMC Sierra configs. I've seen this error on both EC3S and ECSY PMC adapter types. We've only run systems with 6TB drives or a mix of 6TB and 8TB disk drives so far. == Comment: #5 == Call Trace: dmesg -T --- [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] hxestorage D 3fff78c69a20 0 18049 451 0x0004 [Fri Oct 2 12:36:52 2015] Call Trace: [Fri Oct 2 12:36:52 2015] [c0791de17490] [c079111f8980] 0xc079111f8980 (unreliable) [Fri Oct 2 12:36:52 2015] [c0791de17660] [c0015934] __switch_to+0x204/0x350 [Fri Oct 2 12:36:52 2015] [c0791de176c0] [c0a11948] __schedule+0x368/0x8
[Kernel-packages] [Bug 1546343] Re: ISST-LTE: kernel BUG at /build/linux-lts-wily-W0lTWH/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:6016!
Is this issue persisting with newer, supported kernels? ** 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/1546343 Title: ISST-LTE: kernel BUG at /build/linux-lts-wily-W0lTWH/linux-lts- wily-4.2.0/fs/btrfs/extent-tree.c:6016! Status in linux package in Ubuntu: Incomplete Bug description: Mirroring for awareness: Last replicated on the 4.2.0-27-generic #32~14.04.1 kernel We are encountering btrfs panics like the following while doing stress testing: 68:mon> e cpu 0x68: Vector: 700 (Program Check) at [c00029a971d0] pc: d691f7b4: unpin_extent_range+0xe4/0x320 [btrfs] lr: d691f7a4: unpin_extent_range+0xd4/0x320 [btrfs] sp: c00029a97450 msr: 800100029033 current = 0xc000fbdae590 paca= 0xc7b1dc00 softe: 0irq_happened: 0x01 pid = 28091, comm = aio-stress kernel BUG at /build/linux-lts-wily-YKsqw8/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:6022! 68:mon> t [c00029a974e0] d6936a68 btrfs_destroy_pinned_extent+0xe8/0x120 [btrfs] [c00029a97530] d693b8e0 btrfs_cleanup_one_transaction+0x3a0/0x7c0 [btrfs] [c00029a97610] d69405a0 cleanup_transaction+0x150/0x3b0 [btrfs] [c00029a976f0] d694184c btrfs_commit_transaction+0x40c/0xd40 [btrfs] [c00029a977f0] d692910c flush_space+0x10c/0x5f0 [btrfs] [c00029a978b0] d6929b78 reserve_metadata_bytes+0x258/0x640 [btrfs] [c00029a97990] d692a7b0 btrfs_delalloc_reserve_metadata+0x190/0x560 [btrfs] [c00029a97a10] d69591d0 __btrfs_buffered_write+0x1a0/0x5c0 [btrfs] [c00029a97af0] d695c9a8 btrfs_file_write_iter+0x208/0x540 [btrfs] [c00029a97b90] c0327dc0 aio_run_iocb+0x330/0x3c0 [c00029a97ce0] c0329664 do_io_submit+0x314/0x670 [c00029a97e30] c0009204 system_call+0x38/0xb4 --- Exception: c01 (System Call) at 3fffa79e0768 SP (3fffa27ce550) is in userspace 68:mon> r R00 = d691f7a4 R16 = 0d0f R01 = c00029a97450 R17 = c00203badee8 R02 = d6a134d0 R18 = 0060 R03 = R19 = R04 = 0041f20d R20 = R05 = 0001 R21 = 0001 R06 = c001e6d9a409 R22 = c00204c00138 R07 = c001e6d9a400 R23 = c15342d8 R08 = 1500 R24 = 0041f20e R09 = 0001 R25 = 0041f20d R10 = 004200a8 R26 = c00204c0 R11 = d69def18 R27 = R12 = c0a717c0 R28 = c0022fc8e698 R13 = c7b1dc00 R29 = R14 = 10004820 R30 = 0041f20d R15 = c00203badec4 R31 = pc = d691f7b4 unpin_extent_range+0xe4/0x320 [btrfs] cfar= d69174b4 block_group_cache_tree_search+0x104/0x180 [btrfs] lr = d691f7a4 unpin_extent_range+0xd4/0x320 [btrfs] msr = 800100029033 cr = 28022842 ctr = c0a717c0 xer = 2001 trap = 700 Partial Output for dump log: [269404.043284] [ cut here ] [269404.043288] WARNING: at /build/linux-lts-wily-YKsqw8/linux-lts-wily-4.2.0/fs/btrfs/extent-tree.c:3581 [269404.043325] CPU: 104 PID: 28091 Comm: aio-stress Not tainted 4.2.0-27-generic #32~14.04.1-Ubuntu [269404.043329] task: c000fbdae590 ti: c00029a94000 task.ti: c00029a94000 [269404.043331] NIP: d6928fec LR: d6928fe8 CTR: c053f720 [269404.043334] REGS: c00029a97310 TRAP: 0700 Not tainted (4.2.0-27-generic) [269404.043336] MSR: 800100029033 CR: 28044822 XER: 2000 [269404.043346] CFAR: c0a79ec4 SOFTE: 1 [269404.043407] NIP [d6928fec] btrfs_write_dirty_block_groups+0x30c/0x320 [btrfs] [269404.043425] LR [d6928fe8] btrfs_write_dirty_block_groups+0x308/0x320 [btrfs] [269404.043428] Call Trace: [269404.043441] [c00029a97590] [d6928fe8] btrfs_write_dirty_block_groups+0x308/0x320 [btrfs] (unreliable) [269404.043453] [c00029a97660] [d69db42c] commit_cowonly_roots+0x23c/0x324 [btrfs] [269404.043468] [c00029a976f0] [d6941c0c] btrfs_commit_transaction+0x7cc/0xd40 [btrfs] [269404.043483] [c00029a977f0] [d692910c] flush_space+0x10c/0x5f0 [btrfs] [269404.043497] [c00029a978b0] [d6929b78] reserve_metadata_bytes+0x258/0x640 [btrfs] [269404.043511] [c00029a97990] [d692a7b0] btrfs_delalloc_reserve_metadata+0x190/0x560 [btrfs] [269404.043527] [c00029a97a10] [d69591d0] __btrfs_buffered_write+0x1a0/0x5c0 [btrfs] [269404.043541] [c00029a97af0] [d695c9a8] btrfs_file_write_iter+0x208/0x540
[Kernel-packages] [Bug 1505178] Re: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra
** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1505178 Title: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 == When running STX on Habanero systems with PMC Sierra, the following linux error messages are found when running "dmesg -T --level=alert,crit,err" after the run. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18177 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18181 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18185 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18189 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18194 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18200 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18205 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18213 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18221 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. We are running the following code levels. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 14.04.3 LTS \n \l Kernel Version: 3.19.0-25-generic HTX Version: htxubuntu-357 Host Name: rcx2c357 Machine Serial No: 1035C5A Machine Type/Model: 8348-21C We have a very limited number of PMC Sierra configs. I've seen this error on both EC3S and ECSY PMC adapter types. We've only run systems with 6TB drives or a mix of 6TB and 8TB disk drives so far. == Comment: #5 == Call Trace: dmesg -T --- [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] hxestorage D 3fff78c69a20 0 18049 451 0x0004 [Fri Oct 2 12:36:52 2015] Call Trace: [Fri Oct 2 12:36:52 2015] [c0791de17490] [c079111f8980] 0xc079111f8980 (unreliable) [Fri Oct 2 12:36:52 2015] [c0791de17660] [c0015934] __switch_to+0x204/0x350 [Fri Oct 2 12:36:52 2015] [c0791de176c0] [c0a
[Kernel-packages] [Bug 1505178] Re: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra
** Changed in: linux (Ubuntu) Status: Triaged => 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/1505178 Title: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 == When running STX on Habanero systems with PMC Sierra, the following linux error messages are found when running "dmesg -T --level=alert,crit,err" after the run. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18177 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18181 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18185 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18189 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18194 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18200 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18205 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18213 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18221 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. We are running the following code levels. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 14.04.3 LTS \n \l Kernel Version: 3.19.0-25-generic HTX Version: htxubuntu-357 Host Name: rcx2c357 Machine Serial No: 1035C5A Machine Type/Model: 8348-21C We have a very limited number of PMC Sierra configs. I've seen this error on both EC3S and ECSY PMC adapter types. We've only run systems with 6TB drives or a mix of 6TB and 8TB disk drives so far. == Comment: #5 == Call Trace: dmesg -T --- [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] hxestorage D 3fff78c69a20 0 18049 451 0x0004 [Fri Oct 2 12:36:52 2015] Call Trace: [Fri Oct 2 12:36:52 2015] [c0791de17490] [c079111f8980] 0xc079111f8980 (unreliable) [Fri Oct 2 12:36:52 2015] [c0791de17660] [c0015934] __switch_to+0x204/0x350 [Fri Oct 2 12:36:52 2015] [c0791de176c0] [c0a11948] __schedule+0x368/0x8d0
[Kernel-packages] [Bug 1505178] Re: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra
Marking bug as incomplete, as per comment #5, no response was received. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1505178 Title: MFG: Habanero: hxestorage exerciser logs task blocked messages in dmesg when running disks under PMC Sierra Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 == When running STX on Habanero systems with PMC Sierra, the following linux error messages are found when running "dmesg -T --level=alert,crit,err" after the run. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18177 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18181 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18185 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18189 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18194 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18200 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18205 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18213 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18221 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. We are running the following code levels. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 14.04.3 LTS \n \l Kernel Version: 3.19.0-25-generic HTX Version: htxubuntu-357 Host Name: rcx2c357 Machine Serial No: 1035C5A Machine Type/Model: 8348-21C We have a very limited number of PMC Sierra configs. I've seen this error on both EC3S and ECSY PMC adapter types. We've only run systems with 6TB drives or a mix of 6TB and 8TB disk drives so far. == Comment: #5 == Call Trace: dmesg -T --- [Fri Oct 2 12:36:52 2015] INFO: task hxestorage:18049 blocked for more than 120 seconds. [Fri Oct 2 12:36:52 2015] Tainted: G OE 3.19.0-25-generic #26~14.04.1-Ubuntu [Fri Oct 2 12:36:52 2015] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [Fri Oct 2 12:36:52 2015] hxestorage D 3fff78c69a20 0 18049 451 0x0004 [Fri Oct 2 12:36:52 2015] Call Trace: [Fri Oct 2 12:36:52 2015] [c0791de17490] [c079111f8980] 0xc079111f8980 (unreliable) [Fri Oct 2 12:36:52 2015] [c0791de17660] [c0015934] __switch_to+0x204/0x350 [Fri Oct 2 12:36:52 2015] [c0791de176c0] [c0a11948] __schedule+0x368/
[Kernel-packages] [Bug 1537666] Re: ISST-LTE: Ubuntu 14.04.4 LPAR interrupts at check_and_cede_processor
As per comment #4, marking this Fix Released. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1537666 Title: ISST-LTE: Ubuntu 14.04.4 LPAR interrupts at check_and_cede_processor Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-12-11 17:19:07 == ---Problem Description--- We have an Ubuntu 14.04.4 LPAR, conelp2. It is running stress test: base, io, and tcp. When checking "dmesg", we see this interruption: [Fri Dec 11 13:58:50 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 11 13:58:50 2015] LR = check_and_cede_processor+0x34/0x50 In the previous test, conelp2 stopped all the stress tests by itself because it ran out of memory. Is the out of memory issue relating to the interruption? Contact Information = Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com ---uname output--- Linux conelp2 4.2.0-21-generic #25~14.04.1-Ubuntu SMP Thu Dec 3 13:55:42 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = EUH Alpine 8408-E8E ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install Ubuntu 14.04.4 in a LPAR, then update to the latest 14.04.4 kernel by using this workaround: echo "deb http://software.linux.ibm.com/pub/ubuntu-ppc64el-repository/ trusty-proposed main restricted universe multiverse" >> /etc/apt/sources.list apt-get update apt-get install linux-image-generic-lts-wily 2. Setup the Stress test, and start base,io, tcp 3. After an hour, check dmesg, then you will see the message about the interruption Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #1 - YUECHANG E. MEI - 2015-12-11 17:23:00 == == Comment: #3 - YUECHANG E. MEI - 2015-12-14 15:23:33 == == Comment: #4 - MAMATHA INAMDAR - 2015-12-15 03:56:14 == dmrsg show page allocation failure [Fri Dec 11 13:45:38 2015] swapper/127: page allocation failure: order:0, mode:0x120 [Fri Dec 11 13:45:38 2015] CPU: 127 PID: 0 Comm: swapper/127 Not tainted 4.2.0-21-generic #25~14.04.1-Ubuntu [Fri Dec 11 13:45:38 2015] Call Trace: [Fri Dec 11 13:45:38 2015] [c0027fbc3890] [c0a805ec] dump_stack+0x90/0xbc (unreliable) [Fri Dec 11 13:45:38 2015] [c0027fbc38c0] [c021c118] warn_alloc_failed+0x118/0x160 [Fri Dec 11 13:45:38 2015] [c0027fbc3960] [c0221114] __alloc_pages_nodemask+0x834/0xa60 [Fri Dec 11 13:45:38 2015] [c0027fbc3b10] [c0221404] __alloc_page_frag+0xc4/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3b50] [c08f6d20] netdev_alloc_frag+0x50/0x80 [Fri Dec 11 13:45:38 2015] [c0027fbc3b80] [c0764e80] tg3_alloc_rx_data+0xa0/0x2c0 [Fri Dec 11 13:45:38 2015] [c0027fbc3be0] [c0767344] tg3_poll_work+0x484/0x1070 [Fri Dec 11 13:45:38 2015] [c0027fbc3ce0] [c0767f8c] tg3_poll_msix+0x5c/0x210 [Fri Dec 11 13:45:38 2015] [c0027fbc3d30] [c090ebb8] net_rx_action+0x2d8/0x430 [Fri Dec 11 13:45:38 2015] [c0027fbc3e40] [c00ba124] __do_softirq+0x174/0x390 [Fri Dec 11 13:45:38 2015] [c0027fbc3f40] [c00ba6c8] irq_exit+0xc8/0x100 [Fri Dec 11 13:45:38 2015] [c0027fbc3f60] [c00111ec] __do_irq+0x8c/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3f90] [c0024278] call_do_irq+0x14/0x24 [Fri Dec 11 13:45:38 2015] [c002763a39b0] [c0011390] do_IRQ+0xa0/0x120 [Fri Dec 11 13:45:38 2015] [c002763a3a10] [c00099b0] restore_check_irq_replay+0x2c/0x70 [Fri Dec 11 13:45:38 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 11 13:45:38 2015] LR = check_and_cede_processor+0x34/0x50 [Fri Dec 11 13:45:38 2015] [c002763a3d00] [c08a8d90] check_and_cede_processor+0x20/0x50 (unreliable) [Fri Dec 11 13:45:38 2015] [c002763a3d60] [c08a8fb8] shared_cede_loop+0x68/0x170 [Fri Dec 11 13:45:38 2015] [c002763a3da0] [c08a615c] cpuidle_enter_state+0xbc/0x350 [Fri Dec 11 13:45:38 2015] [c002763a3e00] [c0110f3c] call_cpuidle+0x7c/0xd0 [Fri Dec 11 13:45:38 2015] [c002763a3e40] [c01112d0] cpu_startup_entry+0x340/0x450 [Fri Dec 11 13:45:38 2015] [c002763a3f10] [c0044ab4] start_secondary+0x364/0x3a0 [Fri Dec 11 13:45:38 2015] [c002763a3f90
[Kernel-packages] [Bug 1660389] Re: Netgear USB Wifi Adapter Model A6100 AC600 Dual Band
** 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/1660389 Title: Netgear USB Wifi Adapter Model A6100 AC600 Dual Band Status in linux package in Ubuntu: Confirmed Bug description: Bug #1462563 is the same but is closed. I have the device and can send logs. Device will not work. I could do the apport-collect Description: Ubuntu 16.10 Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magne 2271 F pulseaudio betty 30512 F pulseaudio /dev/snd/seq:timidity 1078 F timidity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=b7e1d16d-4f26-4adb-9898-3152ac124149 InstallationDate: Installed on 2016-01-30 (367 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire F5-572G NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=e9242830-11df-4f7d-887d-c812313ff035 ro noprompt persistent quiet splash ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 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-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-16 (107 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 11/06/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd11/06/2015:svnAcer:pnAspireF5-572G:pvrV1.08:rvnAcer:rnZoro_SL:rvrV1.08:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire F5-572G dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661887] Re: AMDGPU support for CIK parts in kernel config?
Emily - The help text for this config option indicates it is still in the experimental/debug phase in v4.4, so I'm not too keen to enable that option in a stable LTS kernel. v4.10 still has the same text, but it is at least an elective install as an HWE kernel in Xenial. We still have some time to test 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/1661887 Title: AMDGPU support for CIK parts in kernel config? Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Hi, I am "nauticalnexus", I'd like to ask for AMDGPU support for CIK(Sea Islands, 390, 290, 290x, 390x, etc) cards in the standard and lowlatency linux kernel. There is no reason for it to be disabled. I've been using it for a long time on various different distributions and kernels and I've had no issues with it. I'd love to see it in the Ubuntu Linux kernel :) Thanks! P.S: I was told to create a bug report for this, I originally asked this as a question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Changed in: crash (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in crash package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Confirmed Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected [Regression] None expected as those modifications are part of the Zesty and upstream version. [Original description of the problem] vmcore captured by kdump cannot be opened with crash: % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic /var/crash/201612282137/dump.201612282137 ... ... base kernel version: 0.8.0 linux_banner: crash: /usr/lib/debug/boot/vmlinux-4 and /var/crash/201612282137/dump.201612282137 do not match! Usage: crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form) crash [OPTION]... [NAMELIST] (live system form) Enter "crash -h" for details. Looks like the 'linux_banner' cannot be understood by crash. And when the vmcore was dumping, this message being showed: [ 729.609196] kdump-tools[5192]: The kernel version is not supported. [ 729.609447] kdump-tools[5192]: The makedumpfile operation may be incomplete. ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump 2. trigger kdump 3. analyse vmcore with crash Userspace tool common name: crash/makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4 Userspace tool obtained from project website: na *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016 utsname: sysname: Linux nodename: boblp1 release: 4.8.0-32-generic version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 machine: ppc64le domainname: (none) base kernel version: 4.8.0 verify_namelist: dumpfile /proc/version: Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11) /usr/lib/debug/boot/vmlinux-4.8.0-32-generic: Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11) hypervisor: (undetermined) crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL ppc64_vmemmap_init: vmemmap base: f000 crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols root@boblp1:/usr/lib/debug/boot# uname -a Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@boblp1:/usr/lib/debug/boot# 1. Missing v4.8 support related patches in crash tool commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66 Author: Dave Anderson Date: Fri Feb 12 14:32:53 2016 -0500 Fix for the changes made to the kernel module structure introduced by this kernel commit for Linux 4.5 and
[Kernel-packages] [Bug 1659614] Re: [Lenovo M700z] Wifi malfunctions after updating system
** Tags removed: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1659614 Title: [Lenovo M700z] Wifi malfunctions after updating system Status in linux package in Ubuntu: Triaged Status in linux-lts-vivid package in Ubuntu: Triaged Bug description: Lenovo M700z (CID 201601-20436) with its pre-installed image. [Steps To Reproduce] Enable the proposed pocket, and then update the system by 'sudo apt-get dist-upgrade' [Expected Result] Wifi works [Actual Result] Wifi malfunctions. The network indicator does not show any wireless AP. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Fri Jan 27 01:28:34 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-m700z-trusty-amd64-20160314-0 InstallationDate: Installed on 2017-01-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.19.0-37-generic.old-dkms' LIVE Binary 20160314-09:31 SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659598] Re: [Dell Computer Corporation Precision 5510] mic malfunctions after updating system
** Tags removed: kernel-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1659598 Title: [Dell Computer Corporation Precision 5510] mic malfunctions after updating system Status in linux package in Ubuntu: Triaged Status in linux-lts-vivid package in Ubuntu: Triaged Bug description: Dell Computer Corporation Precision 5510 (CID 201612-25281 and 201612-25287) with pre-installed image. [Steps To Reproduce] Enable the proposed pocket, and then update the system by 'sudo apt-get dist-upgrade' [Expected Result] The mic works [Actual Result] The mic malfunctions. The mic didn't even record ambient noise. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-80-generic 3.19.0-80.88~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-80.88~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-80-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Fri Jan 27 00:37:34 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2017-01-26 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661887] Re: AMDGPU support for CIK parts in kernel config?
Will there be a fix for Xenial 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/1661887 Title: AMDGPU support for CIK parts in kernel config? Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Hi, I am "nauticalnexus", I'd like to ask for AMDGPU support for CIK(Sea Islands, 390, 290, 290x, 390x, etc) cards in the standard and lowlatency linux kernel. There is no reason for it to be disabled. I've been using it for a long time on various different distributions and kernels and I've had no issues with it. I'd love to see it in the Ubuntu Linux kernel :) Thanks! P.S: I was told to create a bug report for this, I originally asked this as a question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661843] Re: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path'
Specifically, at least this change was lost. https://launchpadlibrarian.net/219224401/dkms_2.2.0.3-1.1ubuntu5.14.04.4_2.2.0.3-1.1ubuntu5.14.04.5.diff.gz There may have been more changes to dkms_apport.py that disappeared too though. -- 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/1661843 Title: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path' Status in dkms package in Ubuntu: Triaged Status in dkms source package in Zesty: Triaged Bug description: It crash after restart of a kernel upgrade. Best regards and thanks ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: dkms 2.3-2 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 3 21:34:58 2017 ExecutablePath: /usr/share/apport/package-hooks/dkms_packages.py InstallationDate: Installed on 2016-10-30 (96 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: python3 /usr/share/apport/package-hooks/dkms_packages.py -m rtl8192eu -v 4.4 -k 4.9.0-16-generic ProcEnviron: LANG=en_US.UTF-8 TERM=linux PATH=(custom, no user) PythonArgs: ['/usr/share/apport/package-hooks/dkms_packages.py', '-m', 'rtl8192eu', '-v', '4.4', '-k', '4.9.0-16-generic'] SourcePackage: dkms Title: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path' Traceback: Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms_packages.py", line 97, in with open(apport.fileutils.make_report_path(report), 'wb') as f: AttributeError: module 'apport.fileutils' has no attribute 'make_report_path' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1661843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661843] Re: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path'
This is a regression of the fix for bug 1499842, the merge from debian overwrote dkms_apport.py and now it is back to its state from before bug 1499842 was fixed. ** Changed in: dkms (Ubuntu) Assignee: (unassigned) => Aron Xu (happyaron) ** Changed in: dkms (Ubuntu) Status: New => Triaged ** Changed in: dkms (Ubuntu) Importance: Medium => High ** Tags added: regression-release ** Also affects: dkms (Ubuntu Zesty) Importance: High Assignee: Aron Xu (happyaron) Status: Triaged -- 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/1661843 Title: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path' Status in dkms package in Ubuntu: Triaged Status in dkms source package in Zesty: Triaged Bug description: It crash after restart of a kernel upgrade. Best regards and thanks ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: dkms 2.3-2 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 3 21:34:58 2017 ExecutablePath: /usr/share/apport/package-hooks/dkms_packages.py InstallationDate: Installed on 2016-10-30 (96 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: python3 /usr/share/apport/package-hooks/dkms_packages.py -m rtl8192eu -v 4.4 -k 4.9.0-16-generic ProcEnviron: LANG=en_US.UTF-8 TERM=linux PATH=(custom, no user) PythonArgs: ['/usr/share/apport/package-hooks/dkms_packages.py', '-m', 'rtl8192eu', '-v', '4.4', '-k', '4.9.0-16-generic'] SourcePackage: dkms Title: dkms_packages.py crashed with AttributeError in __main__: module 'apport.fileutils' has no attribute 'make_report_path' Traceback: Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms_packages.py", line 97, in with open(apport.fileutils.make_report_path(report), 'wb') as f: AttributeError: module 'apport.fileutils' has no attribute 'make_report_path' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1661843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
The fix for bug 1649905 should have helped impove this 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/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel
** Tags removed: kernel-key ** 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/1653162 Title: System won't boot after upgrade to 16.04 with 4.4.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to 16.04.1 the system won't boot. It can't find the root filesystem. I see errors about host adapter dead on the screen many times. This is with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel 3.13.0-105 the system boots just fine. I have mptbios 5.06.04. The CERC card says bios version 4.1-0 [Build 7403] When booting into the ercovery kernel I'm getting error messages about host adapter dead. Eventually I get a message: "aacraid: aac_fib_send: first asynchronous command timed out. Usually a result of a PCI interrupt routing problem update moher board BIOS or consider utilizing one of the SAFE mode kernel options (acpi, apic etc)" Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a post that I saw about these errors. Booting with "noapic" didn't help. Booting with "noapic noacpi" didn't help. I've also tried the dkms modules from Adaptec and that doesn't seem to help either. I can't figure out how to upgrade the firmware or BIOS on the system from Ubuntu either. This may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 InstallationDate: Installed on 2014-02-24 (1039 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.157.6 RfKill: Tags: xenial Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A00 dmi.board.name: 0X7500 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A00 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662186] Re: linux: 3.13.0-109.156 -proposed tracker
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662186 Title: linux: 3.13.0-109.156 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-109.156 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1662186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8
Can you test 3.16.0-23.31: https://launchpad.net/ubuntu/+source/linux/3.16.0-23.31/+build/6478451 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656605 Title: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Today I did our first production 14.04 to 16.04 LTS server upgrade. I had done so a couple of times successfully on test server machines. Upon booting up on the 16.04 system/kernel, after the Grub screen the server console screen is completely blank. Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those hotkeys does toggle through the tty screens. There is no boot process logged to the server console screen. I did have the last 14.04 kernel yet installed, so selected that one from the Grub menu. Booting that 14.04 kernel, then server console display behaves normally. So I suspected perhaps a bum install of the 16.04 kernel. I used the following commands while booted to the 14.04 kernel to reinstall the 16.04 kernel: $ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic linux-image-generic $ sudo apt-get install linux-image-generic Same results booting the 16.04 kernel after those steps. Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662201] [NEW] linux: 4.10.0-7.9 -proposed tracker
Public bug reported: This bug is for tracking the 4.10.0-7.9 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 ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Zesty) Importance: Medium Status: Confirmed ** Tags: block-proposed kernel-release-tracking-bug zesty ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Tags added: zesty ** Changed in: linux (Ubuntu Zesty) Status: New => Confirmed ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662201 Title: linux: 4.10.0-7.9 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testin
[Kernel-packages] [Bug 1662187] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2017-02-06 09:49 EDT--- Hope these info is also helpful... root@ub01:~# ps -ef|grep 146120 root 146120 146073 0 08:56 pts/700:00:00 /usr/bin/dpkg --status-fd 35 --configure initramfs-tools:all root 146125 146120 0 08:56 pts/700:00:00 /bin/sh /var/lib/dpkg/info/initramfs-tools.postinst triggered update-initramfs root 162758 91537 0 09:45 pts/300:00:00 grep --color=auto 146120 root@ub01:~# strace -p 146120 strace: Process 146120 attached wait4(146125, ^Cstrace: Process 146120 detached root@ub01:~# strace -p 146125 strace: Process 146125 attached wait4(-1, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662187 Title: apt-get upgrade hung when it comes to update initramfs Status in linux package in Ubuntu: New Bug description: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662192] [NEW] linux: 3.2.0-122.165 -proposed tracker
Public bug reported: This bug is for tracking the 3.2.0-122.165 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 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lbm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: block-proposed-precise kernel-release-tracking-bug precise ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-precise ** Tags added: precise ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lbm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lbm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Im
[Kernel-packages] [Bug 1662187] lsof.strace output
--- Comment on attachment From y...@cn.ibm.com 2017-02-06 09:32 EDT--- add the lsof strace output of the apt-get process. ** Attachment added: "lsof.strace output" https://bugs.launchpad.net/bugs/1662187/+attachment/4814090/+files/lsof.strace.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662187 Title: apt-get upgrade hung when it comes to update initramfs Status in linux package in Ubuntu: New Bug description: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662187] Comment bridged from LTC Bugzilla
--- Comment From y...@cn.ibm.com 2017-02-06 09:36 EDT--- strace of the apt-get: wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) wait4(146120, 0x3ffc357d854, WNOHANG, NULL) = 0 pselect6(35, [0 32 34], NULL, NULL, {0, 5000}, {[], 8}) = 0 (Timeout) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662187 Title: apt-get upgrade hung when it comes to update initramfs Status in linux package in Ubuntu: New Bug description: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/L
[Kernel-packages] [Bug 1662187] sysctl -a output
Default Comment by Bridge ** Attachment added: "sysctl -a output" https://bugs.launchpad.net/bugs/1662187/+attachment/4814089/+files/sysctl.gzip ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662187 Title: apt-get upgrade hung when it comes to update initramfs Status in linux package in Ubuntu: New Bug description: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661620] Re: CONFIG_NUMA is missing from the 4.8 kernels on s390x
--- Comment From heinz-werner_se...@de.ibm.com 2017-02-06 09:23 EDT--- Original Setting for Ubuntu 16.04 : cat config-4.4.0-59-generic | grep NUMA CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_NUMA_BALANCING=y # CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set CONFIG_NUMA=y # Select NUMA modes CONFIG_NUMA_EMU=y Than changed with Ubuntu 16.10 to $ grep NUMA config-4.8.0-30-generic CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y # CONFIG_NUMA is not set Changed again with Ubuntu 17.04 back to original grep NUMA config-4.9.0-15-generic CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_NUMA_BALANCING=y # CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set CONFIG_NUMA=y # Select NUMA modes CONFIG_NUMA_EMU=y The setting for 16.10 and also for 16.04.2 should be changed to the original once --- Comment From heinz-werner_se...@de.ibm.com 2017-02-06 09:24 EDT--- *** Bug 151232 has been marked as a duplicate of this bug. *** ** Tags added: architecture-s39064 bugnameltc-151262 severity-high targetmilestone-inin1610 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661620 Title: CONFIG_NUMA is missing from the 4.8 kernels on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Status in linux-hwe-edge source package in Yakkety: Invalid Bug description: CONFIG_NUMA is not set in the 4.8 kernels (16.10 & linux-edge) when it should have been, on s390x. It is set in 4.4 (xenial) and 4.9 (zesty). This is regression of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557690 $ grep CONFIG_NUMA -r linux-4.*/debian.master/config/s390x/config.common.s390x linux-4.4.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA=y linux-4.4.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set linux-4.4.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_EMU=y linux-4.8.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA is not set linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA=y linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_BALANCING=y linux-4.9.0/debian.master/config/s390x/config.common.s390x:# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set linux-4.9.0/debian.master/config/s390x/config.common.s390x:CONFIG_NUMA_EMU=y This is a release regression and linux-edge regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1661620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662104] Re: bcmwl 6.30.223.248+bdcom-0ubuntu8 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2
** Changed in: bcmwl (Ubuntu) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu) Importance: Undecided => High ** Changed in: bcmwl (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1662104 Title: bcmwl 6.30.223.248+bdcom-0ubuntu8 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2 Status in bcmwl package in Ubuntu: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/b/bcmwl/20170205_185311_70902@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/i386/b/bcmwl/20170205_185430_70902@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1662104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662186] [NEW] linux: 3.13.0-109.156 -proposed tracker
Public bug reported: This bug is for tracking the 3.13.0-109.156 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 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: block-proposed-trusty kernel-release-tracking-bug trusty ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Tags added: trusty ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-t
[Kernel-packages] [Bug 1662096] Re: ipv6: fix a refcnt leak with peer addr
https://lists.ubuntu.com/archives/kernel-team/2017-February/082343.html ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662096 Title: ipv6: fix a refcnt leak with peer addr Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Zesty: Fix Released Bug description: The following upstream patch is missing in ubuntu-14.04: f24062b07dda ipv6: fix a refcnt leak with peer addr http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f24062b07dda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662187] [NEW] apt-get upgrade hung when it comes to update initramfs
You have been subscribed to a public bug: ---Problem Description--- apt-get upgrade process is hung when it comes to update the initramfs and it never finishes with any error messages. So I have to kill the process and restart it. But the system asks run 'sudo dpkg --configure -a' to correct the problem if I run 'apt-get upgrade' again. I got the same problem with running 'dpkg --configure -a'. root@ub01:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic python-glance-store 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ---uname output--- Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get update apt-get upgrade Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Below is what I have in the /boot directory -rw--- 1 root root 2552549 Oct 19 10:23 System.map-4.4.0-45-generic -rw-r--r-- 1 root root 535651 Oct 19 10:23 abi-4.4.0-45-generic -rw--- 1 root root13824 Nov 21 20:12 bootmap -rw-r--r-- 1 root root65205 Oct 19 10:23 config-4.4.0-45-generic lrwxrwxrwx 1 root root 27 Oct 26 16:52 initrd.img -> initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic -rw-r--r-- 2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic.dpkg-bak -rw-r--r-- 1 root root0 Feb 4 01:47 initrd.img-4.4.0-45-generic.new drwx-- 2 root root12288 Oct 26 16:50 lost+found lrwxrwxrwx 1 root root 24 Oct 26 16:52 vmlinuz -> vmlinuz-4.4.0-45-generic -rw--- 1 root root 3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic Below is the disk space, /boot has enough space. Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.6G 23G 11% /run /dev/mapper/ub01--vg-root 101G 9.9G 87G 11% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/mapper/mpatha-part1 472M 22M 426M 5% /boot cgmfs 100K 0 100K 0% /run/cgmanager/fs tmpfs 26G 0 26G 0% /run/user/1000 tmpfs 26G 0 26G 0% /run/user/1002 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-151243 severity-high targetmilestone-inin--- -- apt-get upgrade hung when it comes to update initramfs https://bugs.launchpad.net/bugs/1662187 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE
I've backported the fix to Ubuntu Zesty ZFS 0.6.5.8 and this patch solves the issues we're seeing. I've given it a soak test with various zfs specific tests and I don't see any regressions. I've asked upstream if this fix be merged into the main ZFS repo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656259 Title: Linux ZFS port doesn't respect RLIMIT_FSIZE Status in Linux: Fix Released Status in linux package in Ubuntu: In Progress Bug description: bash -c 'ulimit -f 1024; yes | head -n2097152' >/path/on/filesystem/under/test On ext4, this test case prints something along the lines of: bash: line 1: 11274 Broken pipe yes 11275 File size limit exceeded(core dumped) | head -n2097152 On ZFS, this test case incorrectly exits zero with no output, demonstrating that ZFS does not respect RLIMIT_FSIZE. I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT, and on those systems this test case correctly generates SIGXFSZ; so it seems that this is a bug in the Linux port of ZFS. (This was discovered while tracking down Launchpad test suite failures under LXD on ZFS. Launchpad uses RLIMIT_FSIZE in one place to guard against bugs that cause debdiff to generate arbitrarily large amounts of output and fill the disk.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 13 10:01:36 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875 InstallationDate: Installed on 2013-03-01 (1413 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1) MachineType: LENOVO 20BXCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET49WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1656259/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661887] Re: AMDGPU support for CIK parts in kernel config?
Looks to be isolated to the specific chip identifiers. Firmware is now included in the linux-firmware package. UBUNTU: [Config] CONFIG_DRM_AMDGPU_CIK=y ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Zesty) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661887 Title: AMDGPU support for CIK parts in kernel config? Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Hi, I am "nauticalnexus", I'd like to ask for AMDGPU support for CIK(Sea Islands, 390, 290, 290x, 390x, etc) cards in the standard and lowlatency linux kernel. There is no reason for it to be disabled. I've been using it for a long time on various different distributions and kernels and I've had no issues with it. I'd love to see it in the Ubuntu Linux kernel :) Thanks! P.S: I was told to create a bug report for this, I originally asked this as a question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659231] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1659231 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/1659231 Title: drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) for Kernel > 4.6 Status in linux package in Ubuntu: Incomplete Bug description: After upgrading driver from 2:2.99.917+git20160325-1ubuntu1 to 2:2.99.917+git20160706-1ubuntu1, Whenever I open ¨Unity-Control-Center¨ makes the system unresponsive for a while and sometimes forever. Same thing happens if I try to open power or sound settings from indicators or when I try to add online accounts in evolution. I can reproduce same with totem. But all other applications are working fine. And everything works in Yakkety. Screencast:https://youtu.be/69PJZf055V8 I am happy to provide any other debugging info. Just don ask to use ¨apport collect¨ as it hangs as well! I can provide details manually through syslog or something. System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960 Integrated Graphics) Graphics driver: i915 Os: Ubuntu 17.04, 32bit UCC: 15.04.0+17.04.20161125.1-0ubuntu1 Edit: If I boot to recovery and use gallium 0.4 on llvmpipe, problem disappears as well. That is why I think itś some sort of graphics issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659231] Re: i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty)
I just tried linux kernel 4.4.21 from mainline ppa. System settings doesn't hang any more. So I am guessing problem lies in kernel > 4.6. Marking it as affected. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Summary changed: - i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) + drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) ** Summary changed: - drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) + drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) for Kernel > 4.6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659231 Title: drm/i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) for Kernel > 4.6 Status in linux package in Ubuntu: Incomplete Bug description: After upgrading driver from 2:2.99.917+git20160325-1ubuntu1 to 2:2.99.917+git20160706-1ubuntu1, Whenever I open ¨Unity-Control-Center¨ makes the system unresponsive for a while and sometimes forever. Same thing happens if I try to open power or sound settings from indicators or when I try to add online accounts in evolution. I can reproduce same with totem. But all other applications are working fine. And everything works in Yakkety. Screencast:https://youtu.be/69PJZf055V8 I am happy to provide any other debugging info. Just don ask to use ¨apport collect¨ as it hangs as well! I can provide details manually through syslog or something. System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960 Integrated Graphics) Graphics driver: i915 Os: Ubuntu 17.04, 32bit UCC: 15.04.0+17.04.20161125.1-0ubuntu1 Edit: If I boot to recovery and use gallium 0.4 on llvmpipe, problem disappears as well. That is why I think itś some sort of graphics issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range
It is still a problem with Ubuntu 16.04.1. -- 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/1487524 Title: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range Status in linux-firmware package in Ubuntu: Fix Released Bug description: On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac on a wily install out of the box, but can't see any APs on the 5GHz range even though there are APs broadcasting on 5Ghz. 03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Subsystem: Apple Inc. Device 0152 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac $ sudo iwlist wlp3s0 scan|grep Freq Frequency:2.412 GHz (Channel 1) Frequency:2.422 GHz (Channel 3) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: boot/vmlinuz-4.1.0-3-generic] ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jbarnett 1545 F pulseaudio /dev/snd/controlC2: jbarnett 1545 F pulseaudio /dev/snd/controlC1: jbarnett 1545 F pulseaudio /dev/snd/controlC0: jbarnett 1545 F pulseaudio CurrentDesktop: GNOME Date: Fri Aug 21 08:46:15 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.146 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659231] [NEW] i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty)
You have been subscribed to a public bug: After upgrading driver from 2:2.99.917+git20160325-1ubuntu1 to 2:2.99.917+git20160706-1ubuntu1, Whenever I open ¨Unity-Control-Center¨ makes the system unresponsive for a while and sometimes forever. Same thing happens if I try to open power or sound settings from indicators or when I try to add online accounts in evolution. I can reproduce same with totem. But all other applications are working fine. And everything works in Yakkety. Screencast:https://youtu.be/69PJZf055V8 I am happy to provide any other debugging info. Just don ask to use ¨apport collect¨ as it hangs as well! I can provide details manually through syslog or something. System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960 Integrated Graphics) Graphics driver: i915 Os: Ubuntu 17.04, 32bit UCC: 15.04.0+17.04.20161125.1-0ubuntu1 Edit: If I boot to recovery and use gallium 0.4 on llvmpipe, problem disappears as well. That is why I think itś some sort of graphics issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: zesty -- i915: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty) https://bugs.launchpad.net/bugs/1659231 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot
Update: I've tried to pass some boot options to kernel, from all of them that I found 2 helped: acpi=off - Boots but wrong screen resolution. acpi=noirq - Works and screen resolution correct. So at the moment I'm staying with acpi=noirq and latest kernel, I hope this problem will be fixed... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633172 Title: Linux 4.8 as in 16.10 hangs during boot Status in linux package in Ubuntu: Confirmed Bug description: I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel seemed to take ages to boot and appears to have hanged. I have managed to boot the system with the older 4.4 kernels from 16.04 just fine without any problems from systemd etc.. Please fix this so I can stop selecting the kernel manually on each boot. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2 InstallationDate: Installed on 2016-02-19 (236 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-43-generic N/A linux-backports-modules-4.4.0-43-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.4.0-43-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628308] Re: PCCT header not found.
https://lkml.org/lkml/2015/9/9/677 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628308 Title: PCCT header not found. Status in linux package in Ubuntu: Confirmed Bug description: [0.114784] PCCT header not found. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2141 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 27 19:34:08 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 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:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly
I also do see this flaky behaviour of rescue mode. The new bug report includes some more information: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1662137 Apparently on my machine systemd runs into a timeout waiting for swap- or non-root partitions. Unfortunately, entering rescue mode from the running system is also not possible as reported in this other bug: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661851 This renders rescue mode practically useless and should certainly be fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609475 Title: Recovery mode won't allow recovery after manually installing the OS incorrectly Status in linux package in Ubuntu: Opinion Bug description: If one manually installs Ubuntu but doesn't install a boot partition, the recovery mode doesn't work. The expectation (perhaps naively) is that the recovery mode is bootable and allows one to fix the situation. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042 InstallationDate: Installed on 2016-08-04 (33 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory 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 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=a91f753b-69af-4125-a03d-0dcb63d55d38 ro net.ifnames=0 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/03/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0054.2016.0503.1546 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-407 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0054.2016.0503.1546:bd05/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-407:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1544701] Re: [REGRESSION] systematically unable to receive files via bluetooth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1544701 Title: [REGRESSION] systematically unable to receive files via bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: I used to be able to send files over bluetooth from my smartphone to my ubuntu laptop. Then at some point bug 958661 appeared, where the undiscoverable setting for receiving files over bluetooth (which cannot be found under any bluetooth-related setting) was turned off without a reason, and also, at random times Ubuntu would start to reject all transfer despite that setting being turned on - but at least there was the workaround to manually switch the setting off and on which would "fix" the issue. Now after upgrading to 15.10 I am simply UNABLE to send any file via bluetooth from the android phone to the ubuntu laptop. ALL transfers systematically fail. On the phone side, sometimes I get "connectuion failed" and sometimes "transfer rejected on target" (I am quoting the messages by memory, so the wording may not be exact). Something as trivial and vital as transfering files over bluetooth is still broken (and gets more broken at every upgrade) after so many years. This is outrageous. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 11 20:14:51 2016 InstallationDate: Installed on 2013-10-11 (853 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to wily on 2016-01-18 (24 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:35370 acl:131 sco:0 events:112 errors:0 TX bytes:5086 acl:26 sco:0 commands:65 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1544701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] kernel03 (s390x.zVM) - tests ran: 16, failed: 15
tests ran: 16, failed: 15; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/kernel03__4.10.0-6.8__2017-02-06_10-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661300] s2lp6g003 (s390x.zKVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.10.0-6.8-generic/s2lp6g003__4.10.0-6.8__2017-02-06_09-44-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661300 Title: linux: 4.10.0-6.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.10.0-6.8 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 kernel-phase:Packaging kernel-phase-changed:Thursday, 02. February 2017 17:47 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1661300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp