[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
I understand that reverting to 21 can solve severe bugs, but since 21 reverting (experienced in Zesty with 164.1 and now in Artful with 165 versions of linux-firmware package) it seems that my connection is sometimes poor (web pages loading hangs, e.g.). With 22 I do not see such hangs or slowdowns. Maybe it caused too a severe kernel hang (CPU lockup) that I got two times in two days in Zesty without any other critical packages upgrading except linux-firmware. But clearly that's hypothetical, although I never got any severe crash like this before during Zesty's alpha-beta-release lifetime. For people like me that do not like 21, move : https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/iwlwifi-8000C-22.ucode to : /lib/firmware and reboot. My hardware : Dell precision 7510 16 Gb ram, intel wifi 8260 -- 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/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Sounds like this have been narrowed down to changes more recent than this, but I have tried 4.10.0-13. So far it is stable. $ uname -a Linux gooseberry 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:28:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ uptime 22:59:30 up 3 days, 1:30, 1 user, load average: 0.80, 0.77, 0.64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux-hwe-edge source package in Zesty: In Progress Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687353] Re: System freezes due to ALSA error and recovers after significant time
The easiest way to reproduce it was in the game Starbound. Teleporting, quickly the computer would freeze. I could freeze the computer in seconds doing this. While the 4.10 kernel available to install with linux-generic- hwe-16.04-edge has this bug, I believe this problem is corrected in the 4.11 kernel I downloaded at http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.11/ I was able to play for many hours without the problem since I installed the kernel version 4.11. There are change notes regarding ALSA on kernel.org, I believe they are related with the problem I was having. Or I am being absurdly lucky or the bug was corrected on upstream. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688695] 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/1688695 Title: Screen back from suspend or hibernate have graphical issue Status in linux package in Ubuntu: Confirmed Bug description: Back from suspend or hibernate I found two main graphical issue: - The screen is pointed white. (Like a layer up my desktop) - All the screen windows have a strange profile and the angle buttons (close, reduce, extend) are missing. I try both with and without nvidia graphic card driver and I found the same problem. I attached an image in order to better understand the issue, feel free to write me for more information. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: emanuele 2014 F...m pulseaudio /dev/snd/controlC1: emanuele 2014 F pulseaudio /dev/snd/controlC0: emanuele 2014 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 06:25:54 2017 HibernationDevice: RESUME=UUID=3d2fe074-bfcc-42cb-b34d-8bb22b4bd99a InstallationDate: Installed on 2016-12-15 (141 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=959c560a-f349-4c00-92e0-44ef10e038db ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-15 (20 days ago) dmi.bios.date: 10/07/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN63WW:bd10/07/2015:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.name: 80N4 dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688695] [NEW] Screen back from suspend or hibernate have graphical issue
Public bug reported: Back from suspend or hibernate I found two main graphical issue: - The screen is pointed white. (Like a layer up my desktop) - All the screen windows have a strange profile and the angle buttons (close, reduce, extend) are missing. I try both with and without nvidia graphic card driver and I found the same problem. I attached an image in order to better understand the issue, feel free to write me for more information. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: emanuele 2014 F...m pulseaudio /dev/snd/controlC1: emanuele 2014 F pulseaudio /dev/snd/controlC0: emanuele 2014 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 06:25:54 2017 HibernationDevice: RESUME=UUID=3d2fe074-bfcc-42cb-b34d-8bb22b4bd99a InstallationDate: Installed on 2016-12-15 (141 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=959c560a-f349-4c00-92e0-44ef10e038db ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-15 (20 days ago) dmi.bios.date: 10/07/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN63WW:bd10/07/2015:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.name: 80N4 dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Screen_Issue" https://bugs.launchpad.net/bugs/1688695/+attachment/4872502/+files/Schermata%20del%202017-05-06%2006-27-46.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688695 Title: Screen back from suspend or hibernate have graphical issue Status in linux package in Ubuntu: New Bug description: Back from suspend or hibernate I found two main graphical issue: - The screen is pointed white. (Like a layer up my desktop) - All the screen windows have a strange profile and the angle buttons (close, reduce, extend) are missing. I try both with and without nvidia graphic card driver and I found the same problem. I attached an image in order to better understand the issue, feel free to write me for more information. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: emanuele 2014 F...m pulseaudio /dev/snd/controlC1: emanuele 2014 F pulseaudio /dev/snd/controlC0: emanuele 2014 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat May 6 06:25:54 2017 HibernationDevice: RESUME=UUID=3d2fe074-bfcc-42cb-b34d-8bb22b4bd99a InstallationDate: Installed on 2016-12-15 (141 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=959c560a-f349-4c00-92e0-44ef10e038db ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-15 (20 days ago) dmi.bios.date: 10/07/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN63WW:bd10/07/2015:svnLENOVO:pn80N4:pvr
[Kernel-packages] [Bug 1669169] Re: package linux-image-4.10.0-9-generic 4.10.0-9.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[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/1669169 Title: package linux-image-4.10.0-9-generic 4.10.0-9.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Ubuntu 4.10.0-9.11-lowlatency 4.10.0 pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 ProcVersionSignature: Ubuntu 4.10.0-9.11-lowlatency 4.10.0 Uname: Linux 4.10.0-9-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3898 F pulseaudio lommers8322 F pulseaudio /dev/snd/controlC0: gdm3898 F pulseaudio lommers8322 F pulseaudio Date: Mon Feb 27 21:37:17 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=9a476750-3204-4068-8b12-47b0ebc08f0d InstallationDate: Installed on 2016-06-24 (250 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: TOSHIBA SATELLITE L50-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-lowlatency root=UUID=affd248b-2269-41bd-a84f-a2d16f078353 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu1 SourcePackage: linux Title: package linux-image-4.10.0-9-generic 4.10.0-9.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.00:bd12/11/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKT4E-06L008DU:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L50-B dmi.product.version: PSKT4E-06L008DU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1669439] Re: package linux-image-extra-4.4.0-65-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.4.0-65-gener
[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/1669439 Title: package linux-image-extra-4.4.0-65-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- image-extra-4.4.0-65-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: Ran my morning update from the CLI as I do every day. No new apps where installed between the yesterday and today ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-65-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: rfcomm nls_utf8 cifs fscache bnep hp_wmi sparse_keymap wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klaus 5315 F pulseaudio Date: Thu Mar 2 06:01:50 2017 DuplicateSignature: package:linux-image-extra-4.4.0-65-generic:(not installed) Unpacking linux-image-extra-4.4.0-65-generic (4.4.0-65.86) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.4.0-65-generic_4.4.0-65.86_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.4.0-65-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.4.0-65-generic.list-new': Operation not permitted HibernationDevice: RESUME=UUID=e05960d5-d585-4894-8b37-5630bb33524a InstallationDate: Installed on 2016-08-24 (189 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8460p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=e88dbab6-fe84-42f9-a7a4-93ece9c3a770 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-extra-4.4.0-65-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-image-extra-4.4.0-65-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.42 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670127] Re: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h
[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/1670127 Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: Dont know why it is broken or how to fix it, but when it stopped working my Wi-Fi stopped working. Having to hard wire the computer to get connection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-62-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf68 1518 F pulseaudio Date: Sun Mar 5 07:41:49 2017 DpkgHistoryLog: Start-Date: 2017-03-05 07:40:59 Commandline: apt-get install -f Requested-By: wolf68 (1000) Install: linux-headers-4.4.0-62-generic:amd64 (4.4.0-62.83, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.59.62, 4.4.0.62.65), linux-headers-4.4.0-62:amd64 (4.4.0-62.83, 4.4.0-62.83) DuplicateSignature: package:linux-headers-4.4.0-62-generic:(not installed) Unpacking linux-headers-4.4.0-62 (4.4.0-62.83) over (4.4.0-62.83) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-62_4.4.0-62.83_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.4.0-62/include/dt-bindings/spmi/spmi.h.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e9f425ba-b6df-4bb9-a18f-405ac1b1573c InstallationDate: Installed on 2016-08-30 (187 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp4s0no wireless extensions. Lsusb: Bus 002 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1564 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=28266855-d72f-4df6-bb23-a31f0c8df94c 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.6 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-62-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-62-generic/include/config/hugetlbfs.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 08CNC9 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1564:pvrA13:rvnDellInc.:rn08CNC9:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1564 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667346] Re: After installation of 4-8-0-39 system crashes after login
[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/1667346 Title: After installation of 4-8-0-39 system crashes after login Status in linux package in Ubuntu: Expired Bug description: I am running Ubuntu 16.04 on a Lenovo W530 thinkpad. I installed the 16.04.2 HWE stack earlier this week; and run fine with kernel 4.8.36 for two, three days. Yesterday, a kernel upgrade to 4.8.39 came in. Installation went fine; but upon reboot; when I try to login ... system does full crash; it only shows my desktop background picture (no mouse pointer, no dash, nothing) and doesn't react to any input any more. I am using the unity desktop; and go with "standard" xserver (no proprietary nvidia driver is used). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
After running for about 24 hours I got a large number of "aacraid: Host adapter abort request (2,0,0,0)" errors and then the following: AAC: Host adapter BLINK LED 0x7 AAC0: adapter kernel panic'd 7. sd 2:0:0:0: Device offlined - not ready after error recovery sd 2:0:0:0: Device offlined - not ready after error recovery sd 2:0:0:0: Device offlined - not ready after error recovery sd 2:0:0:0: Device offlined - not ready after error recovery sd 2:0:0:0: Device offlined - not ready after error recovery sd 2:0:0:0: Device offlined - not ready after error recovery At this point my root filesystem is read-only. It won't reboot remotely because I've got logging turned on for sudo. So I'll need to physically goto the system and do a hard reset. -- You 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: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Yakkety: Incomplete 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.l
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Good news. I have no crashes in 2 days with http://people.canonical.com/~sforshee/lp1674838. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux-hwe-edge source package in Zesty: In Progress Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688643] Re: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04
** Attachment added: "another dmesg trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688643/+attachment/4872445/+files/2017-05-05-kernel-bug.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688643 Title: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04 Status in linux package in Ubuntu: Confirmed Bug description: This has happened to me several times in the last few days since I upgraded from VMWare 12.5.2 and Ubuntu 16.10 to VMWare 12.5.5 and Ubuntu 17.04. The crash has thus far always been associated with firefox and leaves an un-killable zombie firefox process that requires a reboot. 1. The ardware is virtual. (VMWare) 2. I'm not sure how to reproduce it, since it seems to happen randomly, but fairly frequently. 3. The bug didn't occur before the upgrade to VMWare 12.5.5 and Ubuntu 17.04. Please note that I had to run "ubuntu-bug linux" after rebooting because running it before rebooting just hung the process. I will attach a "cut here/end trace" section of the dmesg log separately. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 2006 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri May 5 14:26:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (954 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=ae97a35b-64e3-4db8-ba5f-bcf8b5b94986 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-03 (2 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Awesome. Thank you Milosz for following up there. Perhaps a patch can be created specifically for these boards, something along the lines of 'if board is type am4, vendor==gigabyte: disable pinctrl' Its messy, but it'd work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688663] [NEW] udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Public bug reported: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: 97-hid2hci.rules bluetooth dinovo logitech udev ** Attachment added: "IMG_20170505_181434.jpg" https://bugs.launchpad.net/bugs/1688663/+attachment/4872443/+files/IMG_20170505_181434.jpg -- 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/1688663 Title: udev 97-hid2hci.rules missing usb id for logitech dinovo 2 Status in bluez package in Ubuntu: New Bug description: Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor after being installed using another keyboard and mouse. In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech devices: # Logitech devices KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" # Logitech, Inc. diNovo Edge Keyboard KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" lsusb shows in my computer: Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless Desktop The id is almost equal (c714 <> c704). After adding a new line with the missing id, the keyboard and mouse started to work: # Logitech, Inc. diNovo 2 KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \ RUN+="hid2hci --method=logitech-hid --devpath=%p" I've also followed these other bugs to find out the file that I needed to modify and that my keyboard needs hidraw instead of hiddev: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940 https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
no secure boot. the lenovo t530 is configured for UEFI booting and it works fine. i dont use unity I hate it. I have always used gnome classic (3). before the attempt to fix the bluetooth yesterday the bluetooth menu from the wifi icon on the upper right task bar on Ubuntu 14 gnome 3 at least showed bluetooth. i could also start the applications->systems settings-> bluetooth and get the gnome app and it would at least say there were previous pairing listed on the left (even tho they would not allow data to be exchanged). now in that left list it just says "bluetooth is disabled". I go thru the usual rfkill stuff and all seems OK. the "new driver from github" reports it is good now in dmesg. but I cant find any way to "enable" any ideas? thanks rich On Fri, May 5, 2017 at 4:00 PM, Cruz Fernandez wrote: > Another one, do you have Secure Boot enabled? > > Le ven. 5 mai 2017 à 18:55, Cruz Fernandez a > écrit : > > > Have you tried to use Unity instead of Gnome? > > Le ven. 5 mai 2017 à 18:49, rich painter a > écrit : > > > >> I did this morning. unfortunately some strange side effect has > completely > >> disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the > >> wifi drop down menu at the upper right on the Gnome desktop. I have > tried > >> everything to "enable" bluetooth but to no avail. > >> > >> it seems the problem is now worse. > >> > >> any ideas? > >> > >> thanks > >> rich > >> > >> On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez < > cruz.fernan...@gmail.com> > >> wrote: > >> > >> > @painterengr have you tried to download the file from somewhere else? > >> > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/ > >> > BCM20702A1-0a5c-21e6.hcd > >> > > >> > Hope this is not infringing any legal issues > >> > > >> > Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a > >> > écrit : > >> > > >> > > @painterengr, sorry #165 is not a reply to your comment. It's just > >> > > another related bug for lp:1065400 and I added it here for record. > >> > > > >> > > -- > >> > > You received this bug notification because you are subscribed to the > >> bug > >> > > report. > >> > > https://bugs.launchpad.net/bugs/1065400 > >> > > > >> > > Title: > >> > > Support for loading Broadcom bluetooth firmware > >> > > > >> > > Status in linux package in Ubuntu: > >> > > Fix Released > >> > > Status in linux source package in Precise: > >> > > Fix Released > >> > > Status in linux source package in Quantal: > >> > > Fix Released > >> > > Status in linux source package in Raring: > >> > > Fix Released > >> > > Status in linux source package in Saucy: > >> > > Fix Released > >> > > Status in linux source package in Trusty: > >> > > Confirmed > >> > > > >> > > Bug description: > >> > > Broadcom bluetooth chips require a tool called patchram uploader > [1] > >> > > to load firmware. This applies to at least BCM20702 and BCM43142. > >> > > Although some of the devices have an OTPROM that contains required > >> > > firmware, but it is found that these devices would not have > HFP/HSP > >> > > support unless a upgraded firmware is loaded via patchram > uploader. > >> > > > >> > > This tool requires hci device to do the firmware loading, but this > >> may > >> > > cause some race condition between patchram tool and bluetoothd or > >> > > something that also works on hci interface. > >> > > > >> > > Also it needs some hooks to make firmware loads after bootup, s3, > >> s4, > >> > > rfkill, and device hotplug events. Implement this loader in kernel > >> > > module would make things more easier. > >> > > > >> > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > >> > > > >> > > To manage notifications about this bug go to: > >> > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > >> > 1065400/+subscriptions > >> > > > >> > > >> > -- > >> > You received this bug notification because you are subscribed to the > bug > >> > report. > >> > https://bugs.launchpad.net/bugs/1065400 > >> > > >> > Title: > >> > Support for loading Broadcom bluetooth firmware > >> > > >> > Status in linux package in Ubuntu: > >> > Fix Released > >> > Status in linux source package in Precise: > >> > Fix Released > >> > Status in linux source package in Quantal: > >> > Fix Released > >> > Status in linux source package in Raring: > >> > Fix Released > >> > Status in linux source package in Saucy: > >> > Fix Released > >> > Status in linux source package in Trusty: > >> > Confirmed > >> > > >> > Bug description: > >> > Broadcom bluetooth chips require a tool called patchram uploader [1] > >> > to load firmware. This applies to at least BCM20702 and BCM43142. > >> > Although some of the devices have an OTPROM that contains required > >> > firmware, but it is found that these devices would not have HFP/HSP > >> > support unless a upgraded firmware is loaded via patchram uploader. > >> > > >> > This tool requires hci de
[Kernel-packages] [Bug 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds
@mcumpa could you post the syslog as well as HCI trace for your case? 1. syslog Please enable the debug output first by typing: $ sudo sed -i 's/bluetoothd/bluetoothd \-d/g' /lib/systemd/system/bluetooth.service 2. HCI trace Execute: $ sudo btmon --write ~/hcitrace.snoop before you start reproducing the issue [but might be after pairing to limit the log size]. It is important not to make the test too long so that the HCI trace is easier to read and understand. -- 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/1442896 Title: Bluetooth mouse disconnects and reconnects every few seconds Status in Bluez Utilities: New Status in bluez package in Ubuntu: Incomplete Bug description: I have a bluetooth mouse (Genius Traveller 9005BT) that I have been using without problems with Ubuntu for over a year. Since a few weeks ago, however, it started disconnecting and reconnected from the computer. The symptoms are like this: 1. The mouse works, and the bluetooth icon on the computer is visible (in gnome-shell's top bar) 2. The mouse stops working, but the bluetooth icon is still visible. This state lasts between 1 and 10 seconds. 3. The bluetooth icon vanishes. This can last for half a second if I keep trying to use the mouse, to forever I I leave the mouse alone 4. The bluetooth icon reappears and the mouse starts working again. This state last from 2-3 seconds if I don't move the mouse, to seemingly forever if I continuously move the mouse This seems to occur only after a suspend/resume cycle, and rebooting the computer fixes the issue. The only thing I see in syslog is this when the mouse reconnects: Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 0005:0458:0139.002F: unknown main item tag 0x0 Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59 Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] on e8:2a:ea:8b:a5:5f ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 11 09:49:37 2015 InstallationDate: Installed on 2015-01-23 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: E8:2A:EA:8B:A5:5F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0 TX bytes:29044 acl:238 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1442896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Another one, do you have Secure Boot enabled? Le ven. 5 mai 2017 à 18:55, Cruz Fernandez a écrit : > Have you tried to use Unity instead of Gnome? > Le ven. 5 mai 2017 à 18:49, rich painter a écrit : > >> I did this morning. unfortunately some strange side effect has completely >> disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the >> wifi drop down menu at the upper right on the Gnome desktop. I have tried >> everything to "enable" bluetooth but to no avail. >> >> it seems the problem is now worse. >> >> any ideas? >> >> thanks >> rich >> >> On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez >> wrote: >> >> > @painterengr have you tried to download the file from somewhere else? >> > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/ >> > BCM20702A1-0a5c-21e6.hcd >> > >> > Hope this is not infringing any legal issues >> > >> > Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a >> > écrit : >> > >> > > @painterengr, sorry #165 is not a reply to your comment. It's just >> > > another related bug for lp:1065400 and I added it here for record. >> > > >> > > -- >> > > You received this bug notification because you are subscribed to the >> bug >> > > report. >> > > https://bugs.launchpad.net/bugs/1065400 >> > > >> > > Title: >> > > Support for loading Broadcom bluetooth firmware >> > > >> > > Status in linux package in Ubuntu: >> > > Fix Released >> > > Status in linux source package in Precise: >> > > Fix Released >> > > Status in linux source package in Quantal: >> > > Fix Released >> > > Status in linux source package in Raring: >> > > Fix Released >> > > Status in linux source package in Saucy: >> > > Fix Released >> > > Status in linux source package in Trusty: >> > > Confirmed >> > > >> > > Bug description: >> > > Broadcom bluetooth chips require a tool called patchram uploader [1] >> > > to load firmware. This applies to at least BCM20702 and BCM43142. >> > > Although some of the devices have an OTPROM that contains required >> > > firmware, but it is found that these devices would not have HFP/HSP >> > > support unless a upgraded firmware is loaded via patchram uploader. >> > > >> > > This tool requires hci device to do the firmware loading, but this >> may >> > > cause some race condition between patchram tool and bluetoothd or >> > > something that also works on hci interface. >> > > >> > > Also it needs some hooks to make firmware loads after bootup, s3, >> s4, >> > > rfkill, and device hotplug events. Implement this loader in kernel >> > > module would make things more easier. >> > > >> > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 >> > > >> > > To manage notifications about this bug go to: >> > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ >> > 1065400/+subscriptions >> > > >> > >> > -- >> > You received this bug notification because you are subscribed to the bug >> > report. >> > https://bugs.launchpad.net/bugs/1065400 >> > >> > Title: >> > Support for loading Broadcom bluetooth firmware >> > >> > Status in linux package in Ubuntu: >> > Fix Released >> > Status in linux source package in Precise: >> > Fix Released >> > Status in linux source package in Quantal: >> > Fix Released >> > Status in linux source package in Raring: >> > Fix Released >> > Status in linux source package in Saucy: >> > Fix Released >> > Status in linux source package in Trusty: >> > Confirmed >> > >> > Bug description: >> > Broadcom bluetooth chips require a tool called patchram uploader [1] >> > to load firmware. This applies to at least BCM20702 and BCM43142. >> > Although some of the devices have an OTPROM that contains required >> > firmware, but it is found that these devices would not have HFP/HSP >> > support unless a upgraded firmware is loaded via patchram uploader. >> > >> > This tool requires hci device to do the firmware loading, but this may >> > cause some race condition between patchram tool and bluetoothd or >> > something that also works on hci interface. >> > >> > Also it needs some hooks to make firmware loads after bootup, s3, s4, >> > rfkill, and device hotplug events. Implement this loader in kernel >> > module would make things more easier. >> > >> > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 >> > >> > To manage notifications about this bug go to: >> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ >> > 1065400/+subscriptions >> > >> >> >> -- >> Richard A. Painter, P.E. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1065400 >> >> Title: >> Support for loading Broadcom bluetooth firmware >> >> Status in linux package in Ubuntu: >> Fix Released >> Status in linux source package in Precise: >> Fix Released >> Status in linux source package in Quantal: >> Fix Released >> Status in linux source package in Raring: >> Fix Relea
Re: [Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Have you tried to use Unity instead of Gnome? Le ven. 5 mai 2017 à 18:49, rich painter a écrit : > I did this morning. unfortunately some strange side effect has completely > disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the > wifi drop down menu at the upper right on the Gnome desktop. I have tried > everything to "enable" bluetooth but to no avail. > > it seems the problem is now worse. > > any ideas? > > thanks > rich > > On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez > wrote: > > > @painterengr have you tried to download the file from somewhere else? > > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/ > > BCM20702A1-0a5c-21e6.hcd > > > > Hope this is not infringing any legal issues > > > > Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a > > écrit : > > > > > @painterengr, sorry #165 is not a reply to your comment. It's just > > > another related bug for lp:1065400 and I added it here for record. > > > > > > -- > > > You received this bug notification because you are subscribed to the > bug > > > report. > > > https://bugs.launchpad.net/bugs/1065400 > > > > > > Title: > > > Support for loading Broadcom bluetooth firmware > > > > > > Status in linux package in Ubuntu: > > > Fix Released > > > Status in linux source package in Precise: > > > Fix Released > > > Status in linux source package in Quantal: > > > Fix Released > > > Status in linux source package in Raring: > > > Fix Released > > > Status in linux source package in Saucy: > > > Fix Released > > > Status in linux source package in Trusty: > > > Confirmed > > > > > > Bug description: > > > Broadcom bluetooth chips require a tool called patchram uploader [1] > > > to load firmware. This applies to at least BCM20702 and BCM43142. > > > Although some of the devices have an OTPROM that contains required > > > firmware, but it is found that these devices would not have HFP/HSP > > > support unless a upgraded firmware is loaded via patchram uploader. > > > > > > This tool requires hci device to do the firmware loading, but this > may > > > cause some race condition between patchram tool and bluetoothd or > > > something that also works on hci interface. > > > > > > Also it needs some hooks to make firmware loads after bootup, s3, > s4, > > > rfkill, and device hotplug events. Implement this loader in kernel > > > module would make things more easier. > > > > > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > > 1065400/+subscriptions > > > > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1065400 > > > > Title: > > Support for loading Broadcom bluetooth firmware > > > > Status in linux package in Ubuntu: > > Fix Released > > Status in linux source package in Precise: > > Fix Released > > Status in linux source package in Quantal: > > Fix Released > > Status in linux source package in Raring: > > Fix Released > > Status in linux source package in Saucy: > > Fix Released > > Status in linux source package in Trusty: > > Confirmed > > > > Bug description: > > Broadcom bluetooth chips require a tool called patchram uploader [1] > > to load firmware. This applies to at least BCM20702 and BCM43142. > > Although some of the devices have an OTPROM that contains required > > firmware, but it is found that these devices would not have HFP/HSP > > support unless a upgraded firmware is loaded via patchram uploader. > > > > This tool requires hci device to do the firmware loading, but this may > > cause some race condition between patchram tool and bluetoothd or > > something that also works on hci interface. > > > > Also it needs some hooks to make firmware loads after bootup, s3, s4, > > rfkill, and device hotplug events. Implement this loader in kernel > > module would make things more easier. > > > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > > 1065400/+subscriptions > > > > > -- > Richard A. Painter, P.E. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1065400 > > Title: > Support for loading Broadcom bluetooth firmware > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Precise: > Fix Released > Status in linux source package in Quantal: > Fix Released > Status in linux source package in Raring: > Fix Released > Status in linux source package in Saucy: > Fix Released > Status in linux source package in Trusty: > Confirmed > > Bug description: > Broadcom bluetooth chips require a tool called patchram uploader [1] > to load firmware. This
Re: [Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
I did this morning. unfortunately some strange side effect has completely disabled the bluetooth. I dont even see the Ubuntu bluetooth item on the wifi drop down menu at the upper right on the Gnome desktop. I have tried everything to "enable" bluetooth but to no avail. it seems the problem is now worse. any ideas? thanks rich On Fri, May 5, 2017 at 6:13 AM, Cruz Fernandez wrote: > @painterengr have you tried to download the file from somewhere else? > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/ > BCM20702A1-0a5c-21e6.hcd > > Hope this is not infringing any legal issues > > Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a > écrit : > > > @painterengr, sorry #165 is not a reply to your comment. It's just > > another related bug for lp:1065400 and I added it here for record. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1065400 > > > > Title: > > Support for loading Broadcom bluetooth firmware > > > > Status in linux package in Ubuntu: > > Fix Released > > Status in linux source package in Precise: > > Fix Released > > Status in linux source package in Quantal: > > Fix Released > > Status in linux source package in Raring: > > Fix Released > > Status in linux source package in Saucy: > > Fix Released > > Status in linux source package in Trusty: > > Confirmed > > > > Bug description: > > Broadcom bluetooth chips require a tool called patchram uploader [1] > > to load firmware. This applies to at least BCM20702 and BCM43142. > > Although some of the devices have an OTPROM that contains required > > firmware, but it is found that these devices would not have HFP/HSP > > support unless a upgraded firmware is loaded via patchram uploader. > > > > This tool requires hci device to do the firmware loading, but this may > > cause some race condition between patchram tool and bluetoothd or > > something that also works on hci interface. > > > > Also it needs some hooks to make firmware loads after bootup, s3, s4, > > rfkill, and device hotplug events. Implement this loader in kernel > > module would make things more easier. > > > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1065400/+subscriptions > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1065400 > > Title: > Support for loading Broadcom bluetooth firmware > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Precise: > Fix Released > Status in linux source package in Quantal: > Fix Released > Status in linux source package in Raring: > Fix Released > Status in linux source package in Saucy: > Fix Released > Status in linux source package in Trusty: > Confirmed > > Bug description: > Broadcom bluetooth chips require a tool called patchram uploader [1] > to load firmware. This applies to at least BCM20702 and BCM43142. > Although some of the devices have an OTPROM that contains required > firmware, but it is found that these devices would not have HFP/HSP > support unless a upgraded firmware is loaded via patchram uploader. > > This tool requires hci device to do the firmware loading, but this may > cause some race condition between patchram tool and bluetoothd or > something that also works on hci interface. > > Also it needs some hooks to make firmware loads after bootup, s3, s4, > rfkill, and device hotplug events. Implement this loader in kernel > module would make things more easier. > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1065400/+subscriptions > -- Richard A. Painter, P.E. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause
[Kernel-packages] [Bug 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds
Hi, I use ubuntu 16.04 and I have the same problem. The bluetooth is disconnected and when I try to connect it manually I can not. My laptop is a lenovo z470 and i have the same model of mouse genius traveler 9005bt. ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2017-05-05 15:38:57 PET; 33min ago Docs: man:bluetoothd(8) Main PID: 18775 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─18775 /usr/lib/bluetooth/bluetoothd May 05 15:56:28 cumpa bluetoothd[18775]: Can't get HIDP connection info May 05 15:56:33 cumpa bluetoothd[18775]: connect error: Host is down (112) ** Also affects: bluez Importance: Undecided Status: New -- 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/1442896 Title: Bluetooth mouse disconnects and reconnects every few seconds Status in Bluez Utilities: New Status in bluez package in Ubuntu: Incomplete Bug description: I have a bluetooth mouse (Genius Traveller 9005BT) that I have been using without problems with Ubuntu for over a year. Since a few weeks ago, however, it started disconnecting and reconnected from the computer. The symptoms are like this: 1. The mouse works, and the bluetooth icon on the computer is visible (in gnome-shell's top bar) 2. The mouse stops working, but the bluetooth icon is still visible. This state lasts between 1 and 10 seconds. 3. The bluetooth icon vanishes. This can last for half a second if I keep trying to use the mouse, to forever I I leave the mouse alone 4. The bluetooth icon reappears and the mouse starts working again. This state last from 2-3 seconds if I don't move the mouse, to seemingly forever if I continuously move the mouse This seems to occur only after a suspend/resume cycle, and rebooting the computer fixes the issue. The only thing I see in syslog is this when the mouse reconnects: Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 0005:0458:0139.002F: unknown main item tag 0x0 Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59 Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] on e8:2a:ea:8b:a5:5f ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 11 09:49:37 2015 InstallationDate: Installed on 2015-01-23 (77 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: E8:2A:EA:8B:A5:5F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0 TX bytes:29044 acl:238 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1442896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687901] Re: i915 driver makes linux crash
I can confirm this bug on both Ubuntu 16.04 and 17.04 on Intel Kabylake i7-7500U with Sunrise Point chipset. The 4.11 kernel you suggested fixes the problem, so it is fixed upstream. We should try and backport the fix into at least 16.04 and 17.04. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream 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/1687901 Title: i915 driver makes linux crash Status in linux package in Ubuntu: Confirmed Bug description: I recently upgraded from ubuntu 16.10 to 17.04. Today I got several crash which seems to imply the i915 driver. I had the crash while using gnome-shell, and also while using unity. As I work, the system completely crash. The problem is always in: /build/linux- 2NWldV/linux-4.10.0/drivers/gpu/drm/i915/intel_display.c:4813 skylake_pfit_enable+0x140/0x160 [i915] each time I get the message: [drm:skylake_pfit_enable [i915]] *ERROR* Requesting pfit without getting a scaler first I attach the relevant kern.log parts. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 5651 F pulseaudio /dev/snd/controlC0: alex 5651 F pulseaudio CurrentDesktop: GNOME Date: Wed May 3 11:36:16 2017 HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583 InstallationDate: Installed on 2015-11-10 (539 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-02-25 (66 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Submitted a request with Gigabyte support just now. Can't believe this has been dragging on for two months. Who would have thought to check whether the chosen motherboard even boots up with the latest OS prior to purchasing :\ Extremely frustrating. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688643] 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/1688643 Title: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04 Status in linux package in Ubuntu: Confirmed Bug description: This has happened to me several times in the last few days since I upgraded from VMWare 12.5.2 and Ubuntu 16.10 to VMWare 12.5.5 and Ubuntu 17.04. The crash has thus far always been associated with firefox and leaves an un-killable zombie firefox process that requires a reboot. 1. The ardware is virtual. (VMWare) 2. I'm not sure how to reproduce it, since it seems to happen randomly, but fairly frequently. 3. The bug didn't occur before the upgrade to VMWare 12.5.5 and Ubuntu 17.04. Please note that I had to run "ubuntu-bug linux" after rebooting because running it before rebooting just hung the process. I will attach a "cut here/end trace" section of the dmesg log separately. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 2006 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri May 5 14:26:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (954 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=ae97a35b-64e3-4db8-ba5f-bcf8b5b94986 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-03 (2 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688643] Re: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04
** Attachment added: "dmesg "cut here/end trace" section" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688643/+attachment/4872395/+files/2017-05-04-kernel-bug.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688643 Title: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04 Status in linux package in Ubuntu: New Bug description: This has happened to me several times in the last few days since I upgraded from VMWare 12.5.2 and Ubuntu 16.10 to VMWare 12.5.5 and Ubuntu 17.04. The crash has thus far always been associated with firefox and leaves an un-killable zombie firefox process that requires a reboot. 1. The ardware is virtual. (VMWare) 2. I'm not sure how to reproduce it, since it seems to happen randomly, but fairly frequently. 3. The bug didn't occur before the upgrade to VMWare 12.5.5 and Ubuntu 17.04. Please note that I had to run "ubuntu-bug linux" after rebooting because running it before rebooting just hung the process. I will attach a "cut here/end trace" section of the dmesg log separately. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 2006 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri May 5 14:26:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (954 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=ae97a35b-64e3-4db8-ba5f-bcf8b5b94986 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-03 (2 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688643] [NEW] "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04
Public bug reported: This has happened to me several times in the last few days since I upgraded from VMWare 12.5.2 and Ubuntu 16.10 to VMWare 12.5.5 and Ubuntu 17.04. The crash has thus far always been associated with firefox and leaves an un-killable zombie firefox process that requires a reboot. 1. The ardware is virtual. (VMWare) 2. I'm not sure how to reproduce it, since it seems to happen randomly, but fairly frequently. 3. The bug didn't occur before the upgrade to VMWare 12.5.5 and Ubuntu 17.04. Please note that I had to run "ubuntu-bug linux" after rebooting because running it before rebooting just hung the process. I will attach a "cut here/end trace" section of the dmesg log separately. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 2006 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri May 5 14:26:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (954 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=ae97a35b-64e3-4db8-ba5f-bcf8b5b94986 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-03 (2 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688643 Title: "kernel BUG" reported in dmesg with VMWare and Ubuntu 17.04 Status in linux package in Ubuntu: New Bug description: This has happened to me several times in the last few days since I upgraded from VMWare 12.5.2 and Ubuntu 16.10 to VMWare 12.5.5 and Ubuntu 17.04. The crash has thus far always been associated with firefox and leaves an un-killable zombie firefox process that requires a reboot. 1. The ardware is virtual. (VMWare) 2. I'm not sure how to reproduce it, since it seems to happen randomly, but fairly frequently. 3. The bug didn't occur before the upgrade to VMWare 12.5.5 and Ubuntu 17.04. Please note that I had to run "ubuntu-bug linux" after rebooting because running it before rebooting just hung the process. I will attach a "cut here/end trace" section of the dmesg log separately. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans 2006 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri May 5 14:26:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (954 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=ae97a35b-64e3-4db8-ba5f-bcf8b5b94986 ro quiet splash RelatedPackageVersions: linu
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
Thanks Joseph! I will try it out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter 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: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04 18:28:34 ubuntu kernel: ath: EEPROM indicates we should expect a direct regpair map Mar 04 18:28:34 ubuntu kernel: ath: Country alpha2 being used: 00 Mar 04 18:28:34 ubuntu kernel: ath: Regpair used: 0x6c Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:0
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
I'm trying to follow up with the hardware vendor (Gigabyte) to help us identify the root cause so we can fix it / work around it in the kernel. Here's my last conversation with Matt from Gigabyte: http://forum.gigabyte.us/thread/886/am4-beta-bios- thread?page=47&scrollTo=4429 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
I built a Zesty test kernel with the patch posted in comment 11. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1670041/ Note, with this test kernel you need to install both the linux-image and linux-image-extra .deb packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter 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: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04 18:28:34 ubuntu kernel: ath: EEPROM
[Kernel-packages] [Bug 1679962] Re: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Hmm, I enabled all psmouse protocol detection in that one, apparently it didn't work. Please file an upstream bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679962 Title: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Status in linux package in Ubuntu: Incomplete Bug description: 353/5000 Hello, Randomly the touchpad pointer moves to one end of the screen, and we have found that when it does message appears in dmseg: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Sometimes it happens after 10 minutes of use, sometimes it happens after 3 or 4 hours. We have tested several computers with touchpad "Hantick", that use the both, the evdev library and the libinput library. It always happens randomly. Thanks, ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alejandrolopez 1678 F pulseaudio /dev/snd/controlC1: alejandrolopez 1678 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 5 09:39:01 2017 HibernationDevice: RESUME=UUID=49104028-270a-4546-b219-b38918f339ba InstallationDate: Installed on 2016-04-30 (339 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SLIMBOOK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop quiet i8042.noloop i8042.notimeout i8042.nomux psmouse.resolution=1200 psmouse.resetafter=1 psmouse.rate=50 mousedev.xres=1900 mousedev.yres=800 i8042.reset plymouth:debug drm.debug=0xe RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-11-10 (145 days ago) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pn:pvr1.0:rvnSLIMBOOK:rn:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Status: New => In Progress ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter 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: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM
[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions
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/1688625 Title: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions Status in linux package in Ubuntu: Confirmed Bug description: Hello, We have laptops with touchpad Hantick, that on Miscrosft Windows work with Elan driver. Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions of evdev or libinput. Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slimbook 1720 F pulseaudio CurrentDesktop: Unity Date: Fri May 5 20:01:33 2017 HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448 InstallationDate: Installed on 2017-05-05 (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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SLIMBOOK KATANA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 16L dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: KATANA dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: KATANA dmi.product.version: TBD by OEM dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions
Details with "libinput" $ xinput --list-props 11 Device 'ImExPS/2 Generic Explorer Mouse': Device Enabled (139): 1 Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Accel Speed (275): 1.00 libinput Accel Speed Default (276): 0.00 libinput Accel Profiles Available (277):1, 1 libinput Accel Profile Enabled (278): 1, 0 libinput Accel Profile Enabled Default (279): 1, 0 libinput Natural Scrolling Enabled (280): 0 libinput Natural Scrolling Enabled Default (281): 0 libinput Send Events Modes Available (259): 1, 0 libinput Send Events Mode Enabled (260):0, 0 libinput Send Events Mode Enabled Default (261):0, 0 libinput Left Handed Enabled (282): 0 libinput Left Handed Enabled Default (283): 0 libinput Scroll Methods Available (284):0, 0, 1 libinput Scroll Method Enabled (285): 0, 0, 0 libinput Scroll Method Enabled Default (286): 0, 0, 0 libinput Button Scrolling Button (287): 2 libinput Button Scrolling Button Default (288): 274 libinput Middle Emulation Enabled (289):0 libinput Middle Emulation Enabled Default (290):0 Device Node (262): "/dev/input/event10" Device Product ID (263):2, 6 libinput Drag Lock Buttons (291): libinput Horizonal Scroll Enabled (264):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/1688625 Title: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions Status in linux package in Ubuntu: Confirmed Bug description: Hello, We have laptops with touchpad Hantick, that on Miscrosft Windows work with Elan driver. Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions of evdev or libinput. Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slimbook 1720 F pulseaudio CurrentDesktop: Unity Date: Fri May 5 20:01:33 2017 HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448 InstallationDate: Installed on 2017-05-05 (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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SLIMBOOK KATANA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 16L dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: KATANA dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: KATANA dmi.product.version: TBD by OEM dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions
Details with "evdev" $ xinput --list-props 11 Device 'ImExPS/2 Generic Explorer Mouse': Device Enabled (139): 1 Coordinate Transformation Matrix (141):1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (267):0 Device Accel Constant Deceleration (268): 1.00 Device Accel Adaptive Deceleration (269): 1.00 Device Accel Velocity Scaling (270): 10.00 Device Product ID (259): 2, 6 Device Node (260): "/dev/input/event10" Evdev Axis Inversion (271):0, 0 Evdev Axes Swap (273): 0 Axis Labels (274): "Rel X" (149), "Rel Y" (150), "Rel Horiz Wheel" (265), "Rel Vert Wheel" (266) Button Labels (275): "Button Left" (142), "Button Middle" (143), "Button Right" (144), "Button Wheel Up" (145), "Button Wheel Down" (146), "Button Horiz Wheel Left" (147), "Button Horiz Wheel Right" (148), "Button Side" (263), "Button Extra" (264), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262) Evdev Scrolling Distance (276):1, 1, 1 Evdev Middle Button Emulation (277): 0 Evdev Middle Button Timeout (278): 50 Evdev Third Button Emulation (279):0 Evdev Third Button Emulation Timeout (280):1000 Evdev Third Button Emulation Button (281): 3 Evdev Third Button Emulation Threshold (282): 20 Evdev Wheel Emulation (283): 0 Evdev Wheel Emulation Axes (284): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (285): 10 Evdev Wheel Emulation Timeout (286): 200 Evdev Wheel Emulation Button (287):4 Evdev Drag Lock Buttons (288): 0 ** Description changed: Hello, We have laptops with touchpad Hantick, that on Miscrosft Windows work with Elan driver. Linux does not recognize the Hantick touchpad as a touchpad and does not - enable all the functions of evdeb or libinput. + enable all the functions of evdev or libinput. - With Evdev:: - --- - xinput --list-props 11 - Device 'ImExPS/2 Generic Explorer Mouse': - Device Enabled (139):1 - Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 - Device Accel Profile (267): 0 - Device Accel Constant Deceleration (268):1.00 - Device Accel Adaptive Deceleration (269):1.00 - Device Accel Velocity Scaling (270): 10.00 - Device Product ID (259): 2, 6 - Device Node (260): "/dev/input/event10" - Evdev Axis Inversion (271): 0, 0 - Evdev Axes Swap (273): 0 - Axis Labels (274): "Rel X" (149), "Rel Y" (150), "Rel Horiz Wheel" (265), "Rel Vert Wheel" (266) - Button Labels (275): "Button Left" (142), "Button Middle" (143), "Button Right" (144), "Button Wheel Up" (145), "Button Wheel Down" (146), "Button Horiz Wheel Left" (147), "Button Horiz Wheel Right" (148), "Button Side" (263), "Button Extra" (264), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262) - Evdev Scrolling Distance (276): 1, 1, 1 - Evdev Middle Button Emulation (277): 0 - Evdev Middle Button Timeout (278): 50 - Evdev Third Button Emulation (279): 0 - Evdev Third Button Emulation Timeout (280): 1000 - Evdev Third Button Emulation Button (281): 3 - Evdev Third Button Emulation Threshold (282):20 - Evdev Wheel Emulation (283): 0 - Evdev Wheel Emulation Axes (284):0, 0, 4, 5 - Evdev Wheel Emulation Inertia (285): 10 - Evdev Wheel Emulation Timeout (286): 200 - Evdev Wheel Emulation Button (287): 4 - Evdev Drag Lock Buttons (288): 0 - - --- - - ### More info ### + Thanks + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slimbook 1720 F pulseaudio CurrentDesktop: Unity Date: Fri May 5 20:01:33 2017 HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448 InstallationDate: Installed on 2017-05-05 (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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SLIMBOOK KATANA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-7
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter 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: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04 18:28:34 ubuntu kernel: ath: EEPROM indicates we should expect a direct regpair map Mar 04 18:28:34 ubuntu kernel: ath: Country alpha2 being used: 00 Mar 04 18:28:34 ubuntu kernel: ath:
[Kernel-packages] [Bug 1688625] [NEW] Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions
Public bug reported: Hello, We have laptops with touchpad Hantick, that on Miscrosft Windows work with Elan driver. Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions of evdev or libinput. Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slimbook 1720 F pulseaudio CurrentDesktop: Unity Date: Fri May 5 20:01:33 2017 HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448 InstallationDate: Installed on 2017-05-05 (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 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SLIMBOOK KATANA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 16L dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: KATANA dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: KATANA dmi.product.version: TBD by OEM dmi.sys.vendor: SLIMBOOK ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: Hello, We have laptops with touchpad Hantick, that on Miscrosft Windows work with Elan driver. Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions of evdeb or libinput. With Evdev:: - + --- xinput --list-props 11 Device 'ImExPS/2 Generic Explorer Mouse': - Device Enabled (139): 1 - Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 - Device Accel Profile (267): 0 - Device Accel Constant Deceleration (268): 1.00 - Device Accel Adaptive Deceleration (269): 1.00 - Device Accel Velocity Scaling (270):10.00 - Device Product ID (259):2, 6 - Device Node (260): "/dev/input/event10" - Evdev Axis Inversion (271): 0, 0 - Evdev Axes Swap (273): 0 - Axis Labels (274): "Rel X" (149), "Rel Y" (150), "Rel Horiz Wheel" (265), "Rel Vert Wheel" (266) - Button Labels (275):"Button Left" (142), "Button Middle" (143), "Button Right" (144), "Button Wheel Up" (145), "Button Wheel Down" (146), "Button Horiz Wheel Left" (147), "Button Horiz Wheel Right" (148), "Button Side" (263), "Button Extra" (264), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262), "Button Unknown" (262) - Evdev Scrolling Distance (276): 1, 1, 1 - Evdev Middle Button Emulation (277):0 - Evdev Middle Button Timeout (278): 50 - Evdev Third Button Emulation (279): 0 - Evdev Third Button Emulation Timeout (280): 1000 - Evdev Third Button Emulation Button (281): 3 - Evdev Third Button Emulation Threshold (282): 20 - Evdev Wheel Emulation (283):0 - Evdev Wheel Emulation Axes (284): 0, 0, 4, 5 - Evdev Wheel Emulation Inertia (285):10 - Evdev Wheel Emulation Timeout (286):200 - Evdev Wheel Emulation Button (287): 4 - Evdev Drag Lock Buttons (288): 0 + Device Enabled (139):1 + Coordinate Transformation Matrix (141): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 + Device Accel Profile (267): 0 + Device Accel Constant Deceleration (268):1.00 + Device Accel Adaptive Deceleration (269):1.00 + Device Accel Velocity Scaling (270): 10.00 + Device Product ID (259): 2, 6 + Device Node (260): "/dev/input/event10" + Evdev Axis Inversion (271): 0, 0 + Evdev Axes Swap
[Kernel-packages] [Bug 1687638] Re: Xenial update to 4.4.64 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687638 Title: Xenial update to 4.4.64 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.64 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.64 stable release shall be applied: * KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings * KEYS: Change the name of the dead type to ".dead" to prevent user access * KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings * tracing: Allocate the snapshot buffer before enabling probe * ring-buffer: Have ring_buffer_iter_empty() return true when empty * cifs: Do not send echoes before Negotiate is complete * CIFS: remove bad_network_name flag * s390/mm: fix CMMA vs KSM vs others * VSOCK: Detach QP check should filter out non matching QPs. * Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled * ACPI / power: Avoid maybe-uninitialized warning * mmc: sdhci-esdhc-imx: increase the pad I/O drive strength for DDR50 card * mac80211: reject ToDS broadcast data frames * ubi/upd: Always flush after prepared for an update * powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction * x86/mce/AMD: Give a name to MCA bank 3 when accessed with legacy MSRs * kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions * block: fix del_gendisk() vs blkdev_ioctl crash * tipc: fix crash during node removal * Linux 4.4.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687629] Re: Xenial update to 4.4.63 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687629 Title: Xenial update to 4.4.63 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.63 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.63 stable release shall be applied: * cgroup, kthread: close race window where new kthreads can be migrated to non-root cgroups * thp: fix MADV_DONTNEED vs clear soft dirty race * drm/nouveau/mpeg: mthd returns true on success now * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one * CIFS: store results of cifs_reopen_file to avoid infinite wait * Input: xpad - add support for Razer Wildcat gamepad * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32() * x86/vdso: Ensure vdso32_enabled gets set to valid values only * x86/vdso: Plug race between mapping and ELF header setup * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit comparison) * iscsi-target: Fix TMR reference leak during session shutdown * iscsi-target: Drop work-around for legacy GlobalSAN initiator * scsi: sr: Sanity check returned mode data * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable * scsi: sd: Fix capacity calculation with 32-bit sector_t * xen, fbfront: fix connecting to backend * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat * irqchip/irq-imx-gpcv2: Fix spinlock initialization * ftrace: Fix removing of second function probe * char: Drop bogus dependency of DEVPORT on !M68K * char: lack of bool string made CONFIG_DEVPORT always on * Revert "MIPS: Lantiq: Fix cascaded IRQ setup" * kvm: fix page struct leak in handle_vmon * zram: do not use copy_page with non-page aligned address * powerpc: Disable HFSCR[TM] if TM is not supported * crypto: ahash - Fix EINPROGRESS notification callback * ath9k: fix NULL pointer dereference * dvb-usb-v2: avoid use-after-free * ext4: fix inode checksum calculation problem if i_extra_size is small * platform/x86: acer-wmi: setup accelerometer when machine has appropriate notify event * rtc: tegra: Implement clock handling * mm: Tighten x86 /dev/mem with zeroing reads * dvb-usb: don't use stack for firmware load * dvb-usb-firmware: don't do DMA on stack * virtio-console: avoid DMA from stack * pegasus: Use heap buffers for all register access * rtl8150: Use heap buffers for all register access * catc: Combine failure cleanup code in catc_probe() * catc: Use heap buffer for memory size test * tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done * net: ipv6: check route protocol when deleting routes * MIPS: fix Select HAVE_IRQ_EXIT_ON_IRQ_STACK patch. * Linux 4.4.63 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688483] Re: Xenial update to 4.4.65 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688483 Title: Xenial update to 4.4.65 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.65 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.65 stable release shall be applied: * tipc: make sure IPv6 header fits in skb headroom * tipc: make dist queue pernet * tipc: re-enable compensation for socket receive buffer double counting * tipc: correct error in node fsm * tty: nozomi: avoid a harmless gcc warning * hostap: avoid uninitialized variable use in hfa384x_get_rid * gfs2: avoid uninitialized variable warning * tipc: fix random link resets while adding a second bearer * tipc: fix socket timer deadlock * xc2028: avoid use after free * netfilter: nfnetlink: correctly validate length of batch messages * tipc: check minimum bearer MTU * vfio/pci: Fix integer overflows, bitmask check * staging/android/ion : fix a race condition in the ion driver * ping: implement proper locking * perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race * Linux 4.4.65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670508 Title: CIFS: Enable encryption for SMB3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: There has been work upstream to enable encryption support for SMB3 connections. This is a particularly valuable (and commonly requested) feature with the Azure Files service as encryption is required to connect to an Azure Files storage share from on-prem or from a different Azure region. The relevant commits are as follows: CIFS: Fix possible use after free in demultiplex thread Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5 CIFS: Allow to switch on encryption with seal mount option Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31 CIFS: Add capability to decrypt big read responses Commit c42a6abe3012832a68a371dabe17c2ced97e62ad CIFS: Decrypt and process small encrypted packets Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840 CIFS: Add copy into pages callback for a read operation Commit d70b9104b1ca586f73aaf59426756cec3325a40e CIFS: Add mid handle callback Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e CIFS: Add transform header handling callbacks Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e CIFS: Encrypt SMB3 requests before sending Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398 CIFS: Enable encryption during session setup phase Commit cabfb3680f78981d26c078a26e5c748531257ebb CIFS: Add capability to transform requests before sending Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85 CIFS: Separate RFC1001 length processing for SMB2 read Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6 CIFS: Separate SMB2 sync header processing Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef CIFS: Send RFC1001 length in a separate iov Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf CIFS: Make send_cancel take rqst as argument Commit fb2036d817584df42504910fe104f68517e8990e CIFS: Make SendReceive2() takes resp iov Commit da502f7df03d2d0b416775f92ae022f3f82bedd5 CIFS: Separate SMB2 header structure Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7 cifs: Add soft dependencies Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a cifs: Only select the required crypto modules Commit 3692304bba6164be3810afd41b84ecb0e1e41db1 cifs: Simplify SMB2 and SMB311 dependencies Commit c1ecea87471bbb614f8121e00e5787f363140365 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688505] Re: Xenial update to 4.4.66 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688505 Title: Xenial update to 4.4.66 stable release Status in linux package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.66 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.66 stable release shall be applied: * f2fs: do more integrity verification for superblock * xc2028: unlock on error in xc2028_set_config() * ARM: OMAP2+: timer: add probe for clocksources * clk: sunxi: Add apb0 gates for H3 * crypto: testmgr - fix out of bound read in __test_aead() * drm/amdgpu: fix array out of bounds * ext4: check if in-inode xattr is corrupted in ext4_expand_extra_isize_ea() * md:raid1: fix a dead loop when read from a WriteMostly disk * MIPS: Fix crash registers on non-crashing CPUs * net: cavium: liquidio: Avoid dma_unmap_single on uninitialized ndata * net_sched: close another race condition in tcf_mirred_release() * RDS: Fix the atomicity for congestion map update * regulator: core: Clear the supply pointer if enabling fails * usb: gadget: f_midi: Fixed a bug when buflen was smaller than wMaxPacketSize * xen/x86: don't lose event interrupts * sparc64: kern_addr_valid regression * sparc64: Fix kernel panic due to erroneous #ifdef surrounding pmd_write() * net: neigh: guard against NULL solicit() method * net: phy: handle state correctly in phy_stop_machine * l2tp: purge socket queues in the .destruct() callback * l2tp: take reference on sessions being dumped * l2tp: fix PPP pseudo-wire auto-loading * net: ipv4: fix multipath RTM_GETROUTE behavior when iif is given * sctp: listen on the sock only when it's state is listening or closed * tcp: clear saved_syn in tcp_disconnect() * dp83640: don't recieve time stamps twice * net: ipv6: RTF_PCPU should not be settable from userspace * netpoll: Check for skb->queue_mapping * ip6mr: fix notification device destruction * macvlan: Fix device ref leak when purging bc_queue * ipv6: check skb->protocol before lookup for nexthop * ipv6: check raw payload size correctly in ioctl * ALSA: firewire-lib: fix inappropriate assignment between signed/unsigned type * ALSA: seq: Don't break snd_use_lock_sync() loop by timeout * MIPS: KGDB: Use kernel context for sleeping threads * MIPS: Avoid BUG warning in arch_check_elf * p9_client_readdir() fix * Input: i8042 - add Clevo P650RS to the i8042 reset list * nfsd: check for oversized NFSv2/v3 arguments * ARCv2: save r30 on kernel entry as gcc uses it for code-gen * ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram * Linux 4.4.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688485] Re: Zesty update to 4.10.13 stable release
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688485 Title: Zesty update to 4.10.13 stable release Status in linux package in Ubuntu: New Status in linux source package in Zesty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.13 stable release shall be applied: * KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings * KEYS: Change the name of the dead type to ".dead" to prevent user access * KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings * tracing: Allocate the snapshot buffer before enabling probe * HID: wacom: Treat HID_DG_TOOLSERIALNUMBER as unsigned * ring-buffer: Have ring_buffer_iter_empty() return true when empty * mm: prevent NR_ISOLATE_* stats from going negative * cifs: Do not send echoes before Negotiate is complete * CIFS: remove bad_network_name flag * mmc: dw_mmc: silent verbose log when calling from PM context * s390/mm: fix CMMA vs KSM vs others * Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled * ACPI / power: Avoid maybe-uninitialized warning * mmc: dw_mmc: Don't allow Runtime PM for SDIO cards * mmc: sdhci-esdhc-imx: increase the pad I/O drive strength for DDR50 card * ubifs: Fix RENAME_WHITEOUT support * ubifs: Fix O_TMPFILE corner case in ubifs_link() * mac80211: reject ToDS broadcast data frames * mac80211: fix MU-MIMO follow-MAC mode * x86/mce: Make the MCE notifier a blocking one * ubi/upd: Always flush after prepared for an update * powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction * x86/mce/AMD: Give a name to MCA bank 3 when accessed with legacy MSRs * device-dax: switch to srcu, fix rcu_read_lock() vs pte allocation * Linux 4.10.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683982] Re: net/ipv4: original ingress device index set as the loopback interface.
Hello, Thanks for enabling this patch in proposed. I have performed a verification of the fix on Xenial HWE. With 4.8.0-52 (current linux-generic-hwe-16.04) the error is consistently reproduced, as can be seen in the following lines: root@juju-niedbalski-xenial-machine-30:/home/ubuntu# uname -a Linux juju-niedbalski-xenial-machine-30 4.8.0-52-generic #55~16.04.1-Ubuntu SMP Fri Apr 28 14:36:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@juju-niedbalski-xenial-machine-30:/home/ubuntu# /usr/bin/dhcp_release ns-8382c038-49 192.168.21.14 FA:16:3E:45:6F:AF root@juju-niedbalski-xenial-machine-30:/home/ubuntu# more /var/lib/neutron/dhcp/72dd7d69-9107-45a2-bc0f-43dfe06fcbbb/addn_hosts 192.168.21.1host-192-168-21-1.openstacklocal host-192-168-21-1 192.168.21.2host-192-168-21-2.openstacklocal host-192-168-21-2 192.168.21.6host-192-168-21-6.openstacklocal host-192-168-21-6 192.168.21.14 host-192-168-21-14.openstacklocal host-192-168-21-14 192.168.21.7host-192-168-21-7.openstacklocal host-192-168-21-7 After installing the latest linux-generic-hwe-16.04-edge, the lease is correctly removed, fixing the reported issue. root@juju-niedbalski-xenial-machine-30:/home/ubuntu# uname -a Linux juju-niedbalski-xenial-machine-30 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:57:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@juju-niedbalski-xenial-machine-30:/home/ubuntu# /usr/bin/dhcp_release ns-8382c038-49 192.168.21.6 fa:16:3e:4c:fb:e4 root@juju-niedbalski-xenial-machine-30:/home/ubuntu# more /var/lib/neutron/dhcp/72dd7d69-9107-45a2-bc0f-43dfe06fcbbb/leases 1494092249 fa:16:3e:d0:f7:1b 192.168.21.7 host-192-168-21-7 * 1494092249 fa:16:3e:f8:67:3b 192.168.21.2 host-192-168-21-2 * 1494092249 fa:16:3e:9f:05:3d 192.168.21.1 host-192-168-21-1 * Marking verification-done-yakkety. ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683982 Title: net/ipv4: original ingress device index set as the loopback interface. Status in kolla: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Environment] # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial # uname -a Linux juju-niedbalski-xenial-machine-12 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [Description] We identified a bug in one of the utilities provided by dnsmasq, the 'dhcp_release' utility which is executed as part of the DHCP lease cleanup mechanism by Neutron once a network resource is freed. We noticed that some packets were discarded by the DHCP server (dnsmasq) in Ubuntu systems running a kernel >= 4.7. The reason was the ipi_ifindex field on the pktinfo was incorrectly assumed to be 1 (loopback), this causes the message to be ignored by the dnsmasq daemon since isn't the interface on which dnsmasq is bind to. (gdb) p *p.p $4 = { ipi_ifindex = 1, ipi_spec_dst = { s_addr = 34973888 }, ipi_addr = { s_addr = 34973888 } } (gdb) p ifr $8 = {ifr_ifrn = {ifrn_name = "lo", '\000' }, [Fix] Upstream commit: https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591 [Test Case] 1) Configure a dnsmasq instance to server DHCP (Example): $ sudo dnsmasq --no-hosts --no-resolv --strict-order --except-interface=lo --pid-file=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/host - -addn-hosts=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/opts --dhcp-leasefile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942 518dca/leases --dhcp-match=set:ipxe,175 --bind-interfaces --interface=ns-1cb1b7c7-c0 --dhcp-range=set:tag0,192.168.21.0,static,86400s --dhcp-option-force=option:mtu,1458 --dhcp-lease-max=256 --conf-file=/etc/neutron/dnsmasq.conf -- domain=openstacklocal 2) Boot a VM or container on the bridge/interface on which dnsmasq is bind to. 2) Use the dhcp_release utility to release the lease. (Example): $ sudo dhcp_release ns-1cb1b7c7-c0 192.168.21.8 fa:16:3e:f3:b2:fe The expected result: The lease is freed. Current results: dnsmasq ignored the DHCP Release message. [Fix] When we send a packet for our own local address on a non-loopback interface (e.g. eth0), due to the change had been introduced from commit 0b922b7 ("net: original ingress device index in PKTINFO"), the original ingress device index would be set as t
[Kernel-packages] [Bug 1688499] Re: Zesty update to 4.10.14 stable release
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688499 Title: Zesty update to 4.10.14 stable release Status in linux package in Ubuntu: New Status in linux source package in Zesty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.14 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.14 stable release shall be applied: * ping: implement proper locking * sparc64: kern_addr_valid regression * sparc64: Fix kernel panic due to erroneous #ifdef surrounding pmd_write() * net: neigh: guard against NULL solicit() method * net: phy: handle state correctly in phy_stop_machine * kcm: return immediately after copy_from_user() failure * secure_seq: downgrade to per-host timestamp offsets * bpf: improve verifier packet range checks * Revert "UBUNTU: SAUCE: (no-up) net/mlx5: Avoid dereferencing uninitialized pointer" * net/mlx5: Avoid dereferencing uninitialized pointer * l2tp: hold tunnel socket when handling control frames in l2tp_ip and l2tp_ip6 * l2tp: purge socket queues in the .destruct() callback * openvswitch: Fix ovs_flow_key_update() * l2tp: take reference on sessions being dumped * l2tp: fix PPP pseudo-wire auto-loading * net: ipv4: fix multipath RTM_GETROUTE behavior when iif is given * sctp: listen on the sock only when it's state is listening or closed * tcp: clear saved_syn in tcp_disconnect() * ipv6: Fix idev->addr_list corruption * net-timestamp: avoid use-after-free in ip_recv_error * net: vrf: Fix setting NLM_F_EXCL flag when adding l3mdev rule * sh_eth: unmap DMA buffers when freeing rings * ipv6: sr: fix out-of-bounds access in SRH validation * dp83640: don't recieve time stamps twice * ipv6: sr: fix double free of skb after handling invalid SRH * ipv6: fix source routing * gso: Validate assumption of frag_list segementation * net: ipv6: RTF_PCPU should not be settable from userspace * netpoll: Check for skb->queue_mapping * ip6mr: fix notification device destruction * net/mlx5: Fix driver load bad flow when having fw initializing timeout * net/mlx5: E-Switch, Correctly deal with inline mode on ConnectX-5 * net/mlx5e: Fix small packet threshold * net/mlx5e: Fix ETHTOOL_GRXCLSRLALL handling * tcp: fix SCM_TIMESTAMPING_OPT_STATS for normal skbs * tcp: mark skbs with SCM_TIMESTAMPING_OPT_STATS * macvlan: Fix device ref leak when purging bc_queue * net: ipv6: regenerate host route if moved to gc list * net: phy: fix auto-negotiation stall due to unavailable interrupt * ipv6: check skb->protocol before lookup for nexthop * tcp: memset ca_priv data to 0 properly * ipv6: check raw payload size correctly in ioctl * ALSA: oxfw: fix regression to handle Stanton SCS.1m/1d * ALSA: firewire-lib: fix inappropriate assignment between signed/unsigned type * ALSA: seq: Don't break snd_use_lock_sync() loop by timeout * scsi: return correct blkprep status code in case scsi_init_io() fails. * ARC: [plat-eznps] Fix build error * MIPS: KGDB: Use kernel context for sleeping threads * MIPS: cevt-r4k: Fix out-of-bounds array access * MIPS: Avoid BUG warning in arch_check_elf * p9_client_readdir() fix * ASoC: intel: Fix PM and non-atomic crash in bytcr drivers * Input: i8042 - add Clevo P650RS to the i8042 reset list * nfsd: check for oversized NFSv2/v3 arguments * nfsd4: minor NFSv2/v3 write decoding cleanup * nfsd: stricter decoding of write-like NFSv2/v3 ops * ceph: fix recursion between ceph_set_acl() and __ceph_setattr() * macsec: avoid heap overflow in skb_to_sgvec * net: can: usb: gs_usb: Fix buffer on stack * cpu/hotplug: Serialize callback invocations proper * ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram * Linux 4.10.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687045] Re: Zesty update to 4.10.12 stable release
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687045 Title: Zesty update to 4.10.12 stable release Status in linux package in Ubuntu: New Status in linux source package in Zesty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.12 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.12 stable release shall be applied: * Un-revert "audit: fix auditd/kernel connection state tracking"(1) * cgroup, kthread: close race window where new kthreads can be migrated to non-root cgroups * audit: make sure we don't let the retry queue grow without bounds * tcmu: Fix possible overwrite of t_data_sg's last iov[] * tcmu: Fix wrongly calculating of the base_command_size * tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI case * thp: fix MADV_DONTNEED vs. MADV_FREE race * thp: fix MADV_DONTNEED vs clear soft dirty race * zsmalloc: expand class bit * orangefs: free superblock when mount fails * drm/nouveau/mpeg: mthd returns true on success now * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one * drm/nouveau/kms/nv50: fix setting of HeadSetRasterVertBlankDmi method * drm/nouveau/kms/nv50: fix double dma_fence_put() when destroying plane state * drm/nouveau: initial support (display-only) for GP107 * drm/etnaviv: fix missing unlock on error in etnaviv_gpu_submit() * drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again * CIFS: reconnect thread reschedule itself * CIFS: store results of cifs_reopen_file to avoid infinite wait * Input: xpad - add support for Razer Wildcat gamepad * perf annotate s390: Fix perf annotate error -95 (4.10 regression) * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32() * x86/efi: Don't try to reserve runtime regions * x86/signals: Fix lower/upper bound reporting in compat siginfo * x86/intel_rdt: Fix locking in rdtgroup_schemata_write() * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions * x86/vdso: Ensure vdso32_enabled gets set to valid values only * x86/vdso: Plug race between mapping and ELF header setup * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit comparison) * ACPI / scan: Set the visited flag for all enumerated devices * parisc: fix bugs in pa_memcpy * efi/libstub: Skip GOP with PIXEL_BLT_ONLY format * efi/fb: Avoid reconfiguration of BAR that covers the framebuffer * iscsi-target: Fix TMR reference leak during session shutdown * iscsi-target: Drop work-around for legacy GlobalSAN initiator * scsi: sr: Sanity check returned mode data * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable * scsi: qla2xxx: Add fix to read correct register value for ISP82xx. * scsi: sd: Fix capacity calculation with 32-bit sector_t * target: Avoid mappedlun symlink creation during lun shutdown * xen, fbfront: fix connecting to backend * new privimitive: iov_iter_revert() * make skb_copy_datagram_msg() et.al. preserve ->msg_iter on error * libnvdimm: fix blk free space accounting * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat * libnvdimm: band aid btt vs clear poison locking * can: ifi: use correct register to read rx status * pwm: rockchip: State of PWM clock should synchronize with PWM enabled state * cpufreq: Bring CPUs up even if cpufreq_online() failed * irqchip/irq-imx-gpcv2: Fix spinlock initialization * ftrace: Fix removing of second function probe * drm/i915/gvt: set the correct default value of CTX STATUS PTR * char: lack of bool string made CONFIG_DEVPORT always on * Revert "MIPS: Lantiq: Fix cascaded IRQ setup" * zram: do not use copy_page with non-page aligned address * ftrace: Fix function pid filter on instances * crypto: algif_aead - Fix bogus request dereference in completion function * crypto: xts - Fix use-after-free on EINPROGRESS * crypto: ahash - Fix EINPROGRESS notification callback * crypto: lrw - Fix use-after-free on EINPROGRESS * parisc: Fix get_user() for 64-bit value on 32-bit kernel * dvb-usb-v2: avoid use-after-free * ASoC: Intel: select DW_DMAC_CORE since it's mandatory * platform/x86: acer-wmi: setup accelerometer when machine has appropriate notify event * x86/xen: Fix APIC id mismatch war
[Kernel-packages] [Bug 1683982] Re: net/ipv4: original ingress device index set as the loopback interface.
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683982 Title: net/ipv4: original ingress device index set as the loopback interface. Status in kolla: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Environment] # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial # uname -a Linux juju-niedbalski-xenial-machine-12 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [Description] We identified a bug in one of the utilities provided by dnsmasq, the 'dhcp_release' utility which is executed as part of the DHCP lease cleanup mechanism by Neutron once a network resource is freed. We noticed that some packets were discarded by the DHCP server (dnsmasq) in Ubuntu systems running a kernel >= 4.7. The reason was the ipi_ifindex field on the pktinfo was incorrectly assumed to be 1 (loopback), this causes the message to be ignored by the dnsmasq daemon since isn't the interface on which dnsmasq is bind to. (gdb) p *p.p $4 = { ipi_ifindex = 1, ipi_spec_dst = { s_addr = 34973888 }, ipi_addr = { s_addr = 34973888 } } (gdb) p ifr $8 = {ifr_ifrn = {ifrn_name = "lo", '\000' }, [Fix] Upstream commit: https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591 [Test Case] 1) Configure a dnsmasq instance to server DHCP (Example): $ sudo dnsmasq --no-hosts --no-resolv --strict-order --except-interface=lo --pid-file=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/host - -addn-hosts=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942518dca/opts --dhcp-leasefile=/var/lib/neutron/dhcp/860b0cbb-37c3-4bcb-8345-52b942 518dca/leases --dhcp-match=set:ipxe,175 --bind-interfaces --interface=ns-1cb1b7c7-c0 --dhcp-range=set:tag0,192.168.21.0,static,86400s --dhcp-option-force=option:mtu,1458 --dhcp-lease-max=256 --conf-file=/etc/neutron/dnsmasq.conf -- domain=openstacklocal 2) Boot a VM or container on the bridge/interface on which dnsmasq is bind to. 2) Use the dhcp_release utility to release the lease. (Example): $ sudo dhcp_release ns-1cb1b7c7-c0 192.168.21.8 fa:16:3e:f3:b2:fe The expected result: The lease is freed. Current results: dnsmasq ignored the DHCP Release message. [Fix] When we send a packet for our own local address on a non-loopback interface (e.g. eth0), due to the change had been introduced from commit 0b922b7 ("net: original ingress device index in PKTINFO"), the original ingress device index would be set as the loopback interface. * https://github.com/torvalds/linux/commit/f0c16ba8933ed217c2688b277410b2a37ba81591 To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1683982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688602] Re: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted
** Tags removed: need-duplicate-check -- 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/1688602 Title: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Received error during system upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.9 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 5 11:27:52 2017 Dependencies: DuplicateSignature: package:linux-firmware:1.157.9 Unpacking linux-firmware (1.157.10) over (1.157.9) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.10_all.deb (--unpack): unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-03-04 (426 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1688602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688602] [NEW] package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted
Public bug reported: Received error during system upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.9 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 5 11:27:52 2017 Dependencies: DuplicateSignature: package:linux-firmware:1.157.9 Unpacking linux-firmware (1.157.10) over (1.157.9) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.10_all.deb (--unpack): unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-03-04 (426 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1688602 Title: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Received error during system upgrade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.9 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 5 11:27:52 2017 Dependencies: DuplicateSignature: package:linux-firmware:1.157.9 Unpacking linux-firmware (1.157.10) over (1.157.9) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.10_all.deb (--unpack): unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted InstallationDate: Installed on 2016-03-04 (426 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware 1.157.9 failed to install/upgrade: unable to open '/lib/firmware/iwlwifi-7265D-13.ucode.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1688602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671246] Re: kexec-tools does not build for armhf
Hello Manoj, or anyone else affected, Accepted kexec-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.10-1ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: kexec-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1671246 Title: kexec-tools does not build for armhf Status in kexec-tools package in Ubuntu: Invalid Status in kexec-tools source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: In Progress Bug description: [Impact] On armhf system kexec build fails as follows: gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -I./include -I./util_lib/include -Iinclude/ -I./kexec/libfdt -I./kexec/arch/arm/include -c -MD -o kexec/arch/arm/phys_to_virt.o kexec/arch/arm/phys_to_virt.c make[1]: *** No rule to make target 'kexec/arch/arm/iomem.o', needed by 'build/sbin/kexec'. Stop. The fix for this issue is already upstream: From c901bae8683c59a7bc002bd6a1e3e4b6b7d9c5f1 Mon Sep 17 00:00:00 2001 From: Simon Horman Date: Fri, 9 Dec 2016 10:10:49 +0100 Subject: [PATCH] arm: do not build iomem.o target with no soruce Header files should be added to the distribution but not used to derive targets for compilation. In this an attempt was made to build iomem.o, but iomem.c does not exist so this fails. Fixes: 1574ff1aae4f ("arm: include phys_to_virt.h and iomem.h in distribution") Signed-off-by: Simon Horman Reviewed-by: Pratyush Anand [Test Case] Build kexec-tools package from Xenial/Yakkety source in armhf system. [Regression Potential] Since patch is confined to arm there is a low overall risk of regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1671246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687718 Title: linux: 3.13.0-119.166 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1687719 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1687718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Thanks Andrei. However, I can't run the script. I get the following on the terminal : akli@asus:~$ cd /home/akli/ akli@asus:~$ sudo chmod u+x e200ha_with_sound.sh [sudo] Mot de passe de akli : akli@asus:~$ sudo ./e200ha_with_sound.sh ./e200ha_with_sound.sh: 8: ./e200ha_with_sound.sh: Syntax error: newline unexpected akli@asus:~$ I read and followed the github instructions. Did I miss something to run the script ? Thanks for your help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687718 Title: linux: 3.13.0-119.166 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1687719 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1687718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539843] Re: Asus N551/N751: external microphone does not work
Official support for Ubuntu 15.10 "Wily Werewolf" ended on July 28, 2016. The fix for this issue will be in the 4.12 kernel. Ubuntu 17.10 "Artful Aardvark" is scheduled for release on 19th October 2017 and will be based on a 4.12 or later kernel. If you want to try the 4.12 kernel on Ubuntu 14.04 "Trusty Tahr", when the 4.12 kernel is released you can get it from the mainline kernel PPA page at http://kernel.ubuntu.com /~kernel-ppa/mainline/ and instructions on how to install and uninstall it are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539843 Title: Asus N551/N751: external microphone does not work Status in linux package in Ubuntu: Confirmed Bug description: Asus N551JM In this laptop is combined jack for microphone and headphone. I use headset A4Tech Bloody G500 that nice work in Windows. But in KUBUNTU 15.10 and ubuntu 14.04/15.10 they do not work (work only as headphone). System don't see that i connected headset and in pavucontrol i see only embeded in laptop microphone. http://www.alsa-project.org/db/?f=bcf71e457acf21a40799621a85a53e5817f829f9 --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mogost 1348 F pulseaudio /dev/snd/controlC1: mogost 1348 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=d1115de1-e4fd-4119-8d26-79091505b000 InstallationDate: Installed on 2016-01-30 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. N551JM NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_EN.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed root=UUID=b7b85f18-8c88-4443-8a59-2b3a93642c97 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-25-generic N/A linux-backports-modules-4.2.0-25-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JM.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JM 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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JM 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/1539843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4
** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Zesty) 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/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in linux source package in Xenial: Triaged Status in cloud-init source package in Yakkety: Confirmed Status in linux source package in Yakkety: New Status in cloud-init source package in Zesty: Confirmed Status in linux source package in Zesty: New Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. * cloud-init test case wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg; chmod 755 get-proposed-cloudimg; for release in xenial yakkety zesty; do ./get-proposed-cloudimg $release; MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img ; # ubuntu/passw0rd python3 -c 'from cloudinit.net import get_interfaces_by_mac; print(get_interfaces_by_mac())'; # results in no runtime error and doesn't report vlan interface name done [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1662589] Re: Touchpad not working correctly after kernel upgrade
Hi. Not sure who this request is for as I'm not running yakkety. I could install but I won't have time this week. Thanks, Nick. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662589 Title: Touchpad not working correctly after kernel upgrade Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Since the kernel upgraded from 4.4.0-31-generic the touchpad on my Toshiba Tecra laptop has not been functioning correctly. Whenever I try and do two finger srcolling it also thinks I'm doing a two finger tap to to rightclick, making two finger scrolling almost impossible. It is the same for both kernel updates since 4.4.0-31. If I boot from 4.4.0-31 then the touchpad works fine. If I do an xinput in the later kernels it shows :- ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Microsoft Wired Keyboard 600id=10 [slave pointer (2)] ⎜ ↳ Microsoft Comfort Mouse 6000id=11 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Microsoft Wired Keyboard 600id=9[slave keyboard (3)] ↳ TOSHIBA Web Camera - FHDid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Toshiba input device The AlpsPS/2 devices aren't aren't present when booting with 4.4.0.31: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Microsoft Wired Keyboard 600id=10 [slave pointer (2)] ⎜ ↳ Microsoft Comfort Mouse 6000id=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Microsoft Wired Keyboard 600id=9[slave keyboard (3)] ↳ TOSHIBA Web Camera - FHDid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Toshiba input deviceid=15 [slave keyboard (3)] Any ideas? Thanks. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1867 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5f888cc2-be17-45fe-9b4c-c8cf49eb1db8 InstallationDate: Installed on 2017-02-03 (4 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA TECRA A40-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=7c18c2ca-0cc6-4c2c-80ba-194bbbc22646 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 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: 07/12/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 7.40 dmi.board.asset.tag: 00 dmi.board.name: TECRA A40-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TO
[Kernel-packages] [Bug 1670137] Re: zfs l2arc cache inhibits proper suspend
I am also seeing this issue with zfs and l2arc cache on an NVMe and 4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache cache on NVMe as well, but not with the bcache cache on a SATA SSD. I will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend. This is probably an issue in the NVMe kernel stack. -- 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/1670137 Title: zfs l2arc cache inhibits proper suspend Status in zfs-linux package in Ubuntu: Invalid Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
This bug was fixed in the package linux-firmware - 1.165 --- linux-firmware (1.165) artful; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git ade8332383e228cbdcfc605b5e5ef3aa51211401 - linux-firmware: liquidio: update firmware to v1.4.2 - iwlwifi: update -17 firmware for 3260, 7260 and 7265 - iwlwifi: update -22 firmware for 7265D and up - iwlwifi: add -27 firmware for 3168, 7265D, 8000C and 8265 - linux-firmware/i915: Add HuC 1.07.1398 for SKL - linux-firmware/i915: Add HuC 1.07.1398 for broxton - linux-firmware/i915: HuC on 2.0.1810 for Kabylake - linux-firmware/i915: GuC firmware for Broxton v8.7 - linux-firmware/i915: GuC firmware for Kabylake v9.14 - radeon/amdgpu: update license copyright dates - radeon: add new firmware for SI chips - rtlwifi: rtl8723bs: Add firmware for new driver - qla2xxx: Update firmware version to 8.06.00 - amdgpu: add firmware for polaris12 asics - amdgpu: update VI gfx/sdma firmware - amdgpu: update VI smc/mc firmware - update WHENCE for new amdgpu/polaris12_*.bin firmware - linux-firmware: add firmware for mt76x2 - linux-firmware: update Marvell SD8897-B0 firmware image - linux-firmware: update Marvell PCIe-USB8997 firmware image - amdgpu: add smc firmware for new polaris variants - Revert "amdgpu: update VI smc/mc firmware" - Revert "amdgpu: update VI gfx/sdma firmware" - linux-firmware/i915: Fix Corrupted GuC files. - cxgb4: update firmware to revision 1.16.33.0 - nvidia: add GM20B PMU firmware - nvidia: add GP102/GP104/GP106/GP107 signed firmware - linux-firmware: intel: Add Geminilake audio firmware - linux-firmware: Update firmware patch for Intel Bluetooth, 7265 - linux-firmware: Update firmware patch for Intel Bluetooth,8260 - linux-firmware: Update firmware file for Intel Bluetooth,8265 - brcm: update firmware for BCM43340/1 SDIO devices - ath10k: QCA6174 hw3.0: update board-2.bin - qed: Add firmware 8.15.3.0 - linux-firmware: update Marvell PCIe-USB8997 wifi-only firmware image - linux-firmware: intel: Update Broxton audio firmware - nfp: Add firmware 0.6.1 - mediatek: update MT8173 VPU firmware for unsupported VP9 profiles - nvidia: add GP10B signed firmware - nvidia: fix GP107 signed firmware - linux-firmware: liquidio: update firmware to v1.5.1 - linux-firmware: update Marvell SD8887 firmware image - linux-firmware: update Marvell SD8897-B0 firmware image - rtl_bt: Update firmware for BT part of rtl8822be * intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 (LP: #1647826) - UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode -- Seth Forshee Fri, 05 May 2017 08:43:13 -0500 ** Changed in: linux-firmware (Ubuntu Artful) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Status in linux-firmware source package in Artful: Fix Released Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
Kalle, The chip firmware was a guess based upon somebody else's feedback: http://lists.infradead.org/pipermail/ath10k/2016-January/006714.html It might not be true at all and I have done some investigation after creating this bug report a month ago. My notes from back then: - iperf tcp vs udp performance measurements vary with QCA6174; - iperf (2.0.5 2010) does report 200 Mbit/s on an Intel card (tcp workload); - 200 Mbit/s is achievable on QCA6174 when generating UDP workloads via iperf; - Upload performance (laptop -> router -> server) via rsync over ssh caps at 4 MB/s ~~ 32 Mbit/s at first. May even reach 6 MB/s ~ 48 Mbit/s or 8.5 MB at some point. But it never reaches the peak UDP rates of 200Mbit/s. This might seem ok but the fact is that stats are different for the Intel card. - Download (server -> router -> laptop) performance with rsync caps at 62.69 MB/s (megabytes per second). - This is not a server HDD bottleneck - the destination storage was an SSD. - A TCP workload (iperf -c ) initiated from the server side 578 Mbits/sec to iperf -s on the QCA6174 WNIC side caps at 578 Mbit/s ~ 72 MB/s This maps well to what you are saying about the longstanding problem with ath10k & TCP stack. I will try out the hack to confirm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: Confirmed Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter 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: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct fi
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
Seems, that this package gets included via preseed: tasksel tasksel/first multiselect minimal d-i pkgsel/include string grub2 linux-crashdump openssh-server tcsh ksh gawk vim sysstat lxc debootstrap libcap-ng-utils acpid at bc ethtool libxslt1.1 lxc-templates patch uidmap xz-utils acl iptables ulogd2 ntp nfs-common autofs ldap-utils gdisk zfsutils-linux zfs-initramfs dmidecode Anyway, IMHO it doesn't matter what kind of install - it should not fail to install. BTW: The image used is http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer- amd64/current/images/netboot/netboot.tar.gz I've already added the 'set -x' as shown above. The 1st line of the output shows, how it has been done (because there is no vi[m] available in the install environment), and the remaining lines show the output after resuming the install (I guess, the installer redirects everything to /var/log/syslog, otherwise I wonder, where else the output gets captured.). Anyway, I can see two lines prefixed with a '+', so I guess, that 'set -x' does what it should, but there is simply not more than this. IIUC, it does not hurt, if it fails - can be done later/on demand as well. So why not append a '|| true' or remove it completely from postinstall ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: New Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687910] Re: [Lenovo W520] Linux Freezing Issue At Boot
Tested with mainline v4.11 kernel [0] and this bug exists in mainline kernel, too. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8/linux- image-4.11.0-041100rc8-generic_4.11.0-041100rc8.201704232131_amd64.deb) ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Triaged => 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/1687910 Title: [Lenovo W520] Linux Freezing Issue At Boot Status in linux package in Ubuntu: Confirmed Bug description: Boot error occurs in a 64-bit system and only when certain conditions are met: BIOS/UEFI Settings: Config -> Display -> Graphics Device [Discrete Graphics] -> OS Detection for NVIDIA Optimus [Disabled] Security -> Virtualization -> Intel(R) Virtualization Technology [Enabled] -> Intel(R) VT-d Feature [Enabled] System hangs at boot time either after kernel log shows: [1.043982] ACPI: Video Device [VID1] (multi-head: yes rom: yes post: no) [1.047138] FUJITSU Extended Socket Network Device Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED or later after: [OK] Started Load/Save Screen Backlight Brightness of backlight:nv_backlight. The error occurs randomly (about 50% of all boot tries). The error has already been known for a long time (e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/776999) and has never been fixed. It also occurs for older BIOS/UEFI versions and Ubuntu versions (e.g. 14.04) than shown in the report. Other related reports can be found here: https://bugzilla.kernel.org/show_bug.cgi?id=43054 https://bugzilla.kernel.org/show_bug.cgi?id=156341 https://bugzilla.opensuse.org/show_bug.cgi?id=1022443 https://ubuntuforums.org/showthread.php?t=2044699 https://binaryimpulse.com/2014/08/lenovo-thinkpad-w520-workaround-for-linux-freezing-issue-at-boot/ https://forums.lenovo.com/t5/Linux-Discussion/64-bit-Linux-W520-amp-nVidia/td-p/577789/page/2 A workaround for this issue is to add kernel parameter "nox2apic" to the GRUB_CMDLINE_LINUX_DEFAULT line. Another possible workaround (at least for the first hanging position is to use kernel parameters 'acpi_osi=! acpi_osi="!Windows 2009"' instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: 2040 F pulseaudio /dev/snd/controlC0: 2040 F pulseaudio CurrentDesktop: XFCE Date: Wed May 3 13:03:38 2017 HibernationDevice: RESUME=UUID=19c8581e-f65b-4382-a940-e82a48d9297f MachineType: LENOVO 42844AG ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=2f25428b-c54c-422e-be18-18233f17990d ro nox2apic RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET63WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 42844AG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET63WW(1.43):bd10/20/2016:svnLENOVO:pn42844AG:pvrThinkPadW520:rvnLENOVO:rn42844AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42844AG dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686645 Title: linux: 4.4.0-78.99 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686976] Re: linux: 4.8.0-52.55 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686976 Title: linux: 4.8.0-52.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1686978 derivatives: 1686979 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688579] [NEW] linux-aws/linux-gke incorrectly producing and using linux-*-tools-common/linux-*-cloud-tools-common
Public bug reported: Both linux-aws and linux-gke are producing linux-*-tools-common and linux-*-cloud-tools-common. By shipping common files in this way we create conflicting packages: $ sudo apt-get install linux-tools-generic [...] $ sudo apt-get install linux-tools-gke Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-45 linux-headers-4.4.0-45-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic linux-headers-4.8.0-27 linux-headers-4.8.0-27-generic linux-image-4.4.0-45-generic linux-image-4.4.0-75-generic linux-image-4.8.0-27-generic linux-image-extra-4.4.0-45-generic linux-image-extra-4.4.0-75-generic linux-image-extra-4.8.0-27-generic linux-signed-image-4.4.0-45-generic linux-signed-image-4.4.0-75-generic snap-confine ubuntu-core-launcher Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: linux-gke-tools-4.4.0-1012 linux-gke-tools-common linux-tools-4.4.0-1012-gke The following NEW packages will be installed linux-gke-tools-4.4.0-1012 linux-gke-tools-common linux-tools-4.4.0-1012-gke linux-tools-gke 0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/804 kB of archives. After this operation, 2,344 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 427294 files and directories currently installed.) Preparing to unpack .../linux-gke-tools-common_4.4.0-1012.12_all.deb ... Unpacking linux-gke-tools-common (4.4.0-1012.12) ... dpkg: error processing archive /var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb (--unpack): trying to overwrite '/usr/share/man/man8/x86_energy_perf_policy.8.gz', which is also in package linux-tools-common 4.4.0-77.98 Selecting previously unselected package linux-gke-tools-4.4.0-1012. Preparing to unpack .../linux-gke-tools-4.4.0-1012_4.4.0-1012.12_amd64.deb ... Unpacking linux-gke-tools-4.4.0-1012 (4.4.0-1012.12) ... Selecting previously unselected package linux-tools-4.4.0-1012-gke. Preparing to unpack .../linux-tools-4.4.0-1012-gke_4.4.0-1012.12_amd64.deb ... Unpacking linux-tools-4.4.0-1012-gke (4.4.0-1012.12) ... Selecting previously unselected package linux-tools-gke. Preparing to unpack .../linux-tools-gke_4.4.0.1012.14_amd64.deb ... Unpacking linux-tools-gke (4.4.0.1012.14) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) $ ** Affects: linux (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Affects: linux-aws (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Affects: linux-gke (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Affects: linux-aws (Ubuntu Xenial) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Affects: linux-gke (Ubuntu Xenial) Importance: High Assignee: Andy Whitcroft (apw) Status: Confirmed ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gke (Ubuntu) Importance: Undecided => High ** Changed in: linux-gke (Ubuntu) Status: New => Confirmed ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-aws (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-gke (Ubuntu Xen
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
Nice goldyfruit, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682871 Title: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4 Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in linux source package in Xenial: Triaged Status in cloud-init source package in Yakkety: New Status in linux source package in Yakkety: New Status in cloud-init source package in Zesty: New Status in linux source package in Zesty: New Bug description: [Impact] * When vlan interfaces are created, their mac address is copied from the underlying interface, but it is not marked by kernel as stolen. * When underlying interface MAC address is changed, it does not propagate to the vlan interfaces. [Test Case] * Create vlan interface, check the addr_assign_type sysfs attribute, it should be 2, not 0. * Update the base interface mac address, the mac address of the vlan interface should change too. * cloud-init test case wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg; chmod 755 get-proposed-cloudimg; for release in xenial yakkety zesty; do ./get-proposed-cloudimg $release; MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img ; # ubuntu/passw0rd python3 -c 'from cloudinit.net import get_interfaces_by_mac; print(get_interfaces_by_mac())'; # results in no runtime error and doesn't report vlan interface name done [Regression Potential] * Userspace may rely on non-propagating MAC addresses, and the fact that vlan mac address type is wrongly stated as non-stolen; however this behaviour will be consistent with 4.7+ kernels. [Other Info] * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into v4.4 kernels commit 308453aa9156a3b8ee382c0949befb507a32b0c1 Author: Mike Manning Date: Fri May 27 17:45:07 2016 +0100 vlan: Propagate MAC address to VLANs The MAC address of the physical interface is only copied to the VLAN when it is first created, resulting in an inconsistency after MAC address changes of only newly created VLANs having an up-to-date MAC. The VLANs should continue inheriting the MAC address of the physical interface until the VLAN MAC address is explicitly set to any value. This allows IPv6 EUI64 addresses for the VLAN to reflect any changes to the MAC of the physical interface and thus for DAD to behave as expected. Signed-off-by: Mike Manning Signed-off-by: David S. Miller * Original bug report When attempting to verify sru for bug 1669860, I found that vlans are not properly filtered out by 'get_interfaces_by_mac'. That means that the bug is still present with vlans. The reason for this is that /sys/class/net//addr_assign_type shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8. See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net for doc on addr_assign_type. Related bugs: * bug 1669860: cloud-init attempts to rename bonds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1682871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
I still have systems that are completely locking up when a hyper-v backup is taken even with kernel 4.4.0-77. I'll attach the syslog from one. I also have systems that are not locking up but displaying things like '[sdc] asking for cache data failed', '[sdc] assuming drive cache: write through', 'Dev sdc unable to read RDB block 0'. I believe sdc would be the cdrom drive. Attaching the log for the system that was unresponsive. Backups start around 5:00AM. The system was unresponsive when I came in at 8:00AM. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4872297/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory
[Kernel-packages] [Bug 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
4.10.0-17 should be OK too- my colleague tests all kernels- we run the same hardware except video- I have nvidia card. I forgot to ask him about results, but he didn't complain, so it should be fine. Really, it looks very strange, because I don't see any video related changes from 17 to 20 in changelog. Anyway, next 4 days are holidays here, so we can test only after May 9. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684010 Title: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Status in linux package in Ubuntu: Confirmed Bug description: Just freezes all unity and/or X. Nothing in any logs though. 16.10 worked just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684080] 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/1684080 Title: kernel BUG at /build/linux- Fk60NP/linux-4.10.0/include/linux/swapops.h:129! Status in linux package in Ubuntu: Confirmed Bug description: Yesterday my machine crashed. Analysis reveals that this was a kernel (4.10.0-19-generic #21-Ubuntu SMP x86_64) bug... --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 17435 F pulseaudio guillaume 19236 F pulseaudio DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=34aa2e74-6bb4-4c71-8ceb-a180d7199e68 InstallationDate: Installed on 2012-12-06 (1602 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Latitude E5530 non-vPro Package: linux 3.11.0.23.24 [origin: unknown] PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=62582629-4937-4cc6-b2e1-f9a624d18561 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 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.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty third-party-packages Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to zesty on 2016-11-17 (160 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0XJY67 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn0XJY67:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872293/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872294/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872292/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872290/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872291/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872286/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872281/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872284/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872288/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872289/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872287/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684080] Re: kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684080 Title: kernel BUG at /build/linux- Fk60NP/linux-4.10.0/include/linux/swapops.h:129! Status in linux package in Ubuntu: New Bug description: Yesterday my machine crashed. Analysis reveals that this was a kernel (4.10.0-19-generic #21-Ubuntu SMP x86_64) bug... --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 17435 F pulseaudio guillaume 19236 F pulseaudio DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=34aa2e74-6bb4-4c71-8ceb-a180d7199e68 InstallationDate: Installed on 2012-12-06 (1602 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Latitude E5530 non-vPro Package: linux 3.11.0.23.24 [origin: unknown] PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=62582629-4937-4cc6-b2e1-f9a624d18561 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 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.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty third-party-packages Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to zesty on 2016-11-17 (160 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0XJY67 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn0XJY67:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] Re: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2
apport information ** Tags added: apport-collected xenial ** Description changed: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: peter 1807 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a + InstallationDate: Installed on 2017-03-21 (44 days ago) + InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: Wortmann_AG TERRA_MOBILE_1513A + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-77-generic N/A + linux-backports-modules-4.4.0-77-generic N/A + linux-firmware1.157.8 + Tags: xenial + Uname: Linux 4.4.0-77-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/25/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.05.03 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: W950LU + dmi.board.vendor: Clevo + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Clevo + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: + dmi.product.name: TERRA_MOBILE_1513A + dmi.product.version: 1513A-DE-10010 + dmi.sys.vendor: Wortmann_AG ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872280/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launc
[Kernel-packages] [Bug 1675188] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872283/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872285/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675188] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1675188/+attachment/4872282/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675188 Title: Fn-Buttuns for WLAN and secon Monitor don't work since 16.04.2 Status in linux package in Ubuntu: Incomplete Bug description: I have a Notebook Terra Mobile 1513 A. I have installed Ubuntu Mate 16.04.1 and then updated to 16.04.2 The Fn-Buttons F7 (Monitors) and F11 (WLAN) do not work. When I klick on standby and then start again, WLAN do not work. Then I have to restart the system. With Ubuntu 16.04.1 all these functions worked without problems. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1807 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ae258c2c-41f6-4c6c-a4ab-eb541e0ffd4a InstallationDate: Installed on 2017-03-21 (44 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Wortmann_AG TERRA_MOBILE_1513A Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=615818da-fab0-4171-b85c-fc505c8f02fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-77-generic N/A linux-backports-modules-4.4.0-77-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.4.0-77-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: W950LU dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/25/2015:svnWortmann_AG:pnTERRA_MOBILE_1513A:pvr1513A-DE-10010:rvnClevo:rnW950LU:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.name: TERRA_MOBILE_1513A dmi.product.version: 1513A-DE-10010 dmi.sys.vendor: Wortmann_AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
Hello, I am surprised by a few things : first of all, linux-crashdump, hence kdump-tools, is not installed by default on a server install. So you must have added that step somehow. I have just installed Xenial using the mini.iso network install and kdump-tool is not installed after completion. I installed it without any issue, rebooted and the functionality works as expected. Now your output shows that it is the kernel's post-install trigger that fails, so this is where you should but the -x (add it to the sh -e shebang at the top of the script). Then you can run the following & paste the output here : /etc/kernel/postinst.d/kdump-tools $(uname -r) FYI, this script is responsible for building the smaller initrd used by kdump when rebooting after a crash. ...Louis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: New Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established
* Joseph Salisbury : > I built the next test kernel, up to the following commit: > a80db69e47d764bbcaf2fec54b1f308925e7c490 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1686636/a80db69e47d764bbcaf2fec54b1f308925e7c490 > > Can you test that kernel and report back if it has the bug or not? I > will build the next test kernel based on your test results. This kernel HAS the bug! Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705041331 SMP Thu May 4 17:37:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin https://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686636 Title: outgoing tcp connections sometimes fail to be established Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: I spend the better part of a day debugging this. Symptom: Outgoing connections (ssh, tcp to port 80, to port 8080) fail to establish about 25% of my attempts. I then switched the kernel from linux-image-4.10.0-20-generic (zesty) back to linux-image-4.8.0-49-generic (yakkety) and those problems were gone. I have no iptables rules on my system. I'm using an e1000e over gigabit wired network. Attached is a tcpdump of a connection attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hildeb 3286 F pulseaudio /dev/snd/controlC1: hildeb 3286 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Apr 27 10:42:04 2017 HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3 InstallationDate: Installed on 2014-06-19 (1042 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: FUJITSU ESPRIMO E920 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic root=UUID=e0d7cff3-bbdd-467d-b15b-fb96697320f0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-49-generic N/A linux-backports-modules-4.8.0-49-generic N/A linux-firmware1.164 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-03 (23 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.34.0 for D3222-A1x dmi.board.name: D3222-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3222-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$BK02 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.34.0forD3222-A1x:bd01/08/2015:svnFUJITSU:pnESPRIMOE920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct3:cvrC$BK02: dmi.product.name: ESPRIMO E920 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680549] Re: [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s!
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680549 Title: [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: New Bug description: [IMPACT] Booting Zesty 4.10 kernel on Qualcomm Centriq 2400 ARM64 servers causes soft lockups on multiple CPUs. [ 104.205397] Modules linked in: nls_iso8859_1 cdc_acm bridge stp llc ipmi_ssif ipmi_devintf ipmi_msghandler shpchp hdma hdma_mgmt i2c_qup cppc_cpufreq ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage at803x aes_ce_blk aes_ce_cipher crc32_ce crct10dif_ce ghash_ce sha2_ce sha1_ce mlx5_core devlink ptp pps_core ahci_platform libahci_platform libahci qcom_emac sdhci_acpi sdhci xhci_plat_hcd pinctrl_qdf2xxx fjes aes_neon_blk crypto_simd cryptd [ 104.205442] CPU: 47 PID: 0 Comm: swapper/47 Tainted: G L 4.10.0-16-generic #18ubuntuRC03+.1 [ 104.205443] Hardware name: Qualcomm QDF2400 DP/ABW|SYS|CVR,1DPC|V3 , BIOS XBL.DF.2.0.R3-00153 QDF2400_REL CRM 02/ 8/2017 [ 104.205444] task: 9fa30ed49c00 task.stack: 9fa30ed5c000 [ 104.205447] PC is at _raw_spin_unlock_irqrestore+0x2c/0x38 [ 104.205450] LR is at alloc_iova+0x1cc/0x2a0 [ 104.205451] pc : [] lr : [] pstate: 20400145 [ 104.205452] sp : 9fa31fbecc00 [ 104.205453] x29: 9fa31fbecc00 x28: 000efe46 [ 104.205455] x27: 0040 x26: 000f [ 104.205458] x25: 3f06251f8000 x24: 0001 [ 104.205460] x23: 9fa30da06008 x22: [ 104.205462] x21: 9fa2e2af8740 x20: 9fa30da06008 [ 104.205464] x19: 0140 x18: a5e112c1 [ 104.205466] x17: 4d48a1ed x16: b0f9c455 [ 104.205468] x15: aa4269e9 x14: 85094ac4 [ 104.205471] x13: 9b3b00da x12: 8aae8d9c [ 104.205473] x11: 9fa31fbf90b0 x10: 3f0624eb70eb [ 104.205475] x9 : x8 : 0004 [ 104.205477] x7 : 9fa2e2875400 x6 : [ 104.205479] x5 : 9fa2e2875401 x4 : [ 104.205481] x3 : 9fa2e2a27b00 x2 : 9fa2e2875400 [ 104.205483] x1 : 0140 x0 : f7c2 [ 111.198062] INFO: rcu_sched self-detected stall on CPU [ 111.198971] INFO: rcu_sched detected stalls on CPUs/tasks: [ 111.198977]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 fqs=6805 [ 111.198979]32-...: (1 GPs behind) idle=291/1/0 softirq=469/470 fqs=6805 [ 111.198980](detected by 2, t=15002 jiffies, g=143, c=142, q=6968) [ 111.199000] Task dump for CPU 31: [ 111.199002] swapper/31 R running task0 0 1 0x0002 [ 111.199006] Call trace: [ 111.199012] [] __switch_to+0x98/0xb0 [ 111.199014] [<000b7160dcd2>] 0xb7160dcd2 [ 111.199015] Task dump for CPU 32: [ 111.199016] swapper/32 R running task0 0 1 0x0002 [ 111.199018] Call trace: [ 111.199019] [] __switch_to+0x98/0xb0 [ 111.199020] [<000bcde2fa4e>] 0xbcde2fa4e [ 111.227703]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 fqs=6809 [ 111.234558] (t=15010 jiffies g=143 c=142 q=6968) [ 111.239334] Task dump for CPU 31: [ 111.239335] swapper/31 R running task0 0 1 0x0002 [ 111.239338] Call trace: [ 111.239344] [] dump_backtrace+0x0/0x2b0 [ 111.239346] [] show_stack+0x24/0x30 [ 111.239350] [] sched_show_task+0x128/0x178 [ 111.239352] [] dump_cpu_task+0x48/0x58 [ 111.239356] [] rcu_dump_cpu_stacks+0xbc/0xf0 [ 111.239359] [] rcu_check_callbacks+0x7a8/0x968 [ 111.239362] [] update_process_times+0x34/0x60 [ 111.239365] [] tick_sched_handle.isra.7+0x38/0x70 [ 111.239367] [] tick_sched_timer+0x4c/0x98 [ 111.239369] [] __hrtimer_run_queues+0xe8/0x2e8 [ 111.239371] [] hrtimer_interrupt+0xa8/0x228 [ 111.239376] [] arch_timer_handler_phys+0x3c/0x50 [ 111.239379] [] handle_percpu_devid_irq+0x8c/0x230 [ 111.239383] [] generic_handle_irq+0x34/0x50 [ 111.239385] [] __handle_domain_irq+0x68/0xc0 [ 111.239386] [] gic_handle_irq+0xc4/0x170 [ 111.239388] Exception stack(0x9fa31fa7caa0 to 0x9fa31fa7cbd0) [ 111.239390] caa0: 9fa31fa7cad0 0001 9fa31fa7cc00 3f0624a00974 [ 111.239392] cac0: 20400145 0001 00fe 0140 [ 111.239394] cae0: 9fa2e10b1c00 9fa2e11c8800 9fa2e10b1c01 [ 111.239396]
[Kernel-packages] [Bug 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size
The proposed fix is part of upstream v4.5, so included in Yakkety/16,10 onwards. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (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/1687877 Title: bonding - mlx5 - speed changed to 0 after changing ring size Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: The problem happens when changing the ring size of a mlx5_core interface that is part of a LACP bond. [268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143: Link up [268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port enp66s0f1 [268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1 the upstream commit "bonding: allow notifications for bond_set_slave_link_state " fix the issue, will cherry-pick and send to xenial git tree. Thanks, Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687718] Re: linux: 3.13.0-119.166 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1687719 derivatives: - kernel-stable-phase-changed:Wednesday, 03. May 2017 12:31 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 05. May 2017 13:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1687719 derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 05. May 2017 13:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687718 Title: linux: 3.13.0-119.166 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1687719 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1687718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
Now I understand your use-case. You probably could achieve similar with $ systemctl status bluetooth.service. Also hcitool can tell if the adapter is up and running but keep in mind that hcitool is depreciated and no longer maintained by the upstream. As for the man entry suggestion yes that could be something to consider given that the default man page is quite vague nevertheless this, as whole bluez, comes straight from the upstream. -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Thank you very much, I saw there that you probably need the DSDT. I extracted it with sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat Please find it attached. ** Attachment added: "dsdt.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456/+attachment/4872277/+files/dsdt.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5
[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25
all I know it's queued for 4.12: https://bugs.freedesktop.org/show_bug.cgi?id=100516#c2 but that's for mainline kernel, whether ubuntu backports it i donno -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30 17:44:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640 InstallationDate: Installed on 2015-11-02 (514 days ago) InstallationMedia: Ub
[Kernel-packages] [Bug 1679962] Re: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away.
Hello, Nothing has changed. Attached information. Thank you very much. ** Attachment added: "files.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679962/+attachment/4872276/+files/files.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679962 Title: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Status in linux package in Ubuntu: Incomplete Bug description: 353/5000 Hello, Randomly the touchpad pointer moves to one end of the screen, and we have found that when it does message appears in dmseg: psmouse serio1: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Sometimes it happens after 10 minutes of use, sometimes it happens after 3 or 4 hours. We have tested several computers with touchpad "Hantick", that use the both, the evdev library and the libinput library. It always happens randomly. Thanks, ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alejandrolopez 1678 F pulseaudio /dev/snd/controlC1: alejandrolopez 1678 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 5 09:39:01 2017 HibernationDevice: RESUME=UUID=49104028-270a-4546-b219-b38918f339ba InstallationDate: Installed on 2016-04-30 (339 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SLIMBOOK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=d9619f09-3283-4f88-a9aa-a614f1b40470 ro elevator=noop quiet i8042.noloop i8042.notimeout i8042.nomux psmouse.resolution=1200 psmouse.resetafter=1 psmouse.rate=50 mousedev.xres=1900 mousedev.yres=800 i8042.reset plymouth:debug drm.debug=0xe RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-11-10 (145 days ago) dmi.bios.date: 11/21/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: h dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrh:bd11/21/2014:svnSLIMBOOK:pn:pvr1.0:rvnSLIMBOOK:rn:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: dmi.product.version: 1.0 dmi.sys.vendor: SLIMBOOK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Testing on AX370-Gaming K5-CF : 4.10.0-21 compiled by kaihengfeng on http://people.canonical.com/~khfeng/lp1671360-2/ seems working, using it to post result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
My particular use case is to detect, inside a shell script, if there is any bluetooth hardware at all. Since 'bluetoothctl' systematically hangs when there is NO bluetooth hardware, I can NOT use the 'bluetoothctl' command to achieve this use case. But I have found a good alternate method : if rfkill list | grep -q -i Bluetooth; then ...; fi So, the issue is NOT blocking for me. But I suggest that 'man bluetoothctl' should indicate that 'bluetoothctl' waits (possibly indefinitely) for answers from the 'bluetoothd' daemon, and therefore is NOT adequate for scripting. -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
What will it take to get this bug fixed!? Upstream most likely is (or will) point at the hardware vendors (I don't know, thats just me guessing), while the hardware vendor says 'not our problem, we don't support linux'. What are we to do? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
@painterengr have you tried to download the file from somewhere else? https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-0a5c-21e6.hcd Hope this is not infringing any legal issues Le ven. 5 mai 2017 à 04:49, Jesse Sung <1065...@bugs.launchpad.net> a écrit : > @painterengr, sorry #165 is not a reply to your comment. It's just > another related bug for lp:1065400 and I added it here for record. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1065400 > > Title: > Support for loading Broadcom bluetooth firmware > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Precise: > Fix Released > Status in linux source package in Quantal: > Fix Released > Status in linux source package in Raring: > Fix Released > Status in linux source package in Saucy: > Fix Released > Status in linux source package in Trusty: > Confirmed > > Bug description: > Broadcom bluetooth chips require a tool called patchram uploader [1] > to load firmware. This applies to at least BCM20702 and BCM43142. > Although some of the devices have an OTPROM that contains required > firmware, but it is found that these devices would not have HFP/HSP > support unless a upgraded firmware is loaded via patchram uploader. > > This tool requires hci device to do the firmware loading, but this may > cause some race condition between patchram tool and bluetoothd or > something that also works on hci interface. > > Also it needs some hooks to make firmware loads after bootup, s3, s4, > rfkill, and device hotplug events. Implement this loader in kernel > module would make things more easier. > > [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
~ # sed -i.orig -e '/^set/ a\set -x' /target/var/lib/dpkg/info/kdump-tools.postinst ~ # tail -f /var/log/syslog May 5 12:11:29 in-target: linux-crashdump depends on kdump-tools; however: May 5 12:11:29 in-target: Package kdump-tools is not configured yet. May 5 12:11:29 in-target: May 5 12:11:29 in-target: dpkg: error processing package linux-crashdump (--configure): May 5 12:11:29 in-target: dependency problems - leaving unconfigured May 5 12:11:29 in-target: Errors were encountered while processing: May 5 12:11:29 in-target: kdump-tools May 5 12:11:29 in-target: linux-crashdump May 5 12:11:29 main-menu[422]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 5 12:11:29 main-menu[422]: WARNING **: Menu item 'pkgsel' failed. May 5 12:13:15 main-menu[422]: INFO: Modifying debconf priority limit from 'critical' to 'high' May 5 12:13:15 debconf: Setting debconf/priority to high May 5 12:13:15 main-menu[422]: INFO: Falling back to the package description for brltty-udeb May 5 12:13:20 main-menu[422]: INFO: Falling back to the package description for brltty-udeb May 5 12:13:20 main-menu[422]: INFO: Menu item 'pkgsel' selected May 5 12:13:21 in-target: Reading package lists... May 5 12:13:21 in-target: May 5 12:13:21 in-target: Building dependency tree... May 5 12:13:21 in-target: May 5 12:13:21 in-target: Reading state information... May 5 12:13:21 in-target: May 5 12:13:21 in-target: tasksel is already the newest version (3.34ubuntu3). May 5 12:13:21 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. May 5 12:13:21 in-target: 2 not fully installed or removed. May 5 12:13:21 in-target: After this operation, 0 B of additional disk space will be used. May 5 12:13:21 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M May 5 12:13:21 in-target: + uname -r^M May 5 12:13:21 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic^M May 5 12:13:21 in-target: dpkg: error processing package kdump-tools (--configure):^M May 5 12:13:21 in-target: subprocess installed post-installation script returned error exit status 1^M May 5 12:13:21 in-target: No apport report written because the error message indicates its a followup error from a previous failure. May 5 12:13:21 in-target: dpkg: dependency problems prevent configuration of linux-crashdump:^M May 5 12:13:21 in-target: linux-crashdump depends on kdump-tools; however:^M May 5 12:13:21 in-target: Package kdump-tools is not configured yet.^M May 5 12:13:21 in-target: ^M May 5 12:13:21 in-target: dpkg: error processing package linux-crashdump (--configure):^M May 5 12:13:21 in-target: dependency problems - leaving unconfigured^M May 5 12:13:21 in-target: Errors were encountered while processing:^M May 5 12:13:21 in-target: kdump-tools^M May 5 12:13:21 in-target: linux-crashdump^M May 5 12:13:22 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 5 12:13:22 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 5 12:13:22 in-target: + uname -r May 5 12:13:22 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic May 5 12:13:22 in-target: dpkg: error processing package kdump-tools (--configure): May 5 12:13:22 in-target: subprocess installed post-installation script returned error exit status 1 May 5 12:13:22 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 5 12:13:22 in-target: linux-crashdump depends on kdump-tools; however: May 5 12:13:22 in-target: Package kdump-tools is not configured yet. May 5 12:13:22 in-target: May 5 12:13:22 in-target: dpkg: error processing package linux-crashdump (--configure): May 5 12:13:22 in-target: dependency problems - leaving unconfigured May 5 12:13:22 in-target: Errors were encountered while processing: May 5 12:13:22 in-target: kdump-tools May 5 12:13:22 in-target: linux-crashdump May 5 12:13:24 pkgsel: checking for (security) updates to the base system May 5 12:13:25 in-target: Reading package lists... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Building dependency tree... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Reading state information... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Calculating upgrade... May 5 12:13:25 in-target: May 5 12:13:25 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. May 5 12:13:25 in-target: 2 not fully installed or removed. May 5 12:13:25 in-target: After this operation, 0 B of additional disk space will be used. May 5 12:13:25 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M May 5 12:13:25 in-target: + uname -r^M May 5 12:13:25 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic^M May 5 12:13:25 in-target: dpkg: error processing package kdump-tools (--configure):^M May 5 12:13:25 in-target: subprocess installed post-installation script returned error exit status 1^M May 5 12:13:2
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Tested on AX370-Gaming K5-CF : Default Ubuntu kernel do not work. 4.10.0-21 compiled by kaihengfeng [http://people.canonical.com/~khfeng/lp1671360/] also shows "unexpected irq trap at vector 07" error message, can not boot to desktop. Both kernel compiled by nextized worked: http://www.nextized.net/repo/linux/ubuntu-linux-4.10.3_ryzen01_amd64_generic.tar.gz http://www.nextized.net/repo/linux/ubuntu-linux-4.11.0_ryzen01_amd64_generic.tar.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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25
With that comment do you mean to say you're positive that 4.12 will have a fix, or do you mean to say you're positive that 4.11 will NOT have a fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30 17:44:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640 InstallationDate: Installed on 2015-11-02 (514 days ago) InstallationMedia: Ubuntu 15.
[Kernel-packages] [Bug 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking
...by closing the display while in the dock", not the "bug" :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1604313 Title: Ubuntu 16.04: system freezes instead of suspend after undocking Status in linux package in Ubuntu: Fix Released Bug description: I'm using a Lenovo ThinkPad T450s. When the system was docked and then undocked, suspend won't work. Instead, the screen goes black, the system freezes and the fan runs on high speed. This problem persists with the (as of today) most recent kernel 4.4.0-31-generic #50. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buerger3534 F pulseaudio /dev/snd/pcmC1D0p: buerger3534 F...m pulseaudio /dev/snd/controlC1: buerger3534 F pulseaudio CurrentDesktop: Unity Date: Tue Jul 19 11:13:41 2016 HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c InstallationDate: Installed on 2015-09-15 (307 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BX000XGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (87 days ago) dmi.bios.date: 03/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: JBET57WW (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp