[Kernel-packages] [Bug 1645322] Re: Synaptics touchpad not detected in Clevo P650RS laptop
Problem persists in 17.04, kernel 4.10.0-19. Workaround is still effective though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1645322 Title: Synaptics touchpad not detected in Clevo P650RS laptop Status in linux package in Ubuntu: Incomplete Bug description: The laptop Clevo P650RS has a Synaptics touchpad but it is not detected by the kernel 4.8.0-27 on Ubuntu 16.10. There is no entry in /proc/bus/input/devices matching it. I installed Windows to check if it works at all, and it does. Windows identifies it as ACPI/SYN1219. WORKAROUND: Use kernel boot parameter: i8042.reset --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chfast27815 F pulseaudio /dev/snd/pcmC0D0p: chfast27815 F...m pulseaudio /dev/snd/controlC0: chfast27815 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=50613b4d-8b7f-4f75-b05a-193836f3ba1a InstallationDate: Installed on 2016-11-26 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Notebook P65_67RSRP NonfreeKernelModules: clevo_xsm_wmi nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04
This time, apport-collect appears to have worked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670315] Comment bridged from LTC Bugzilla
--- Comment From sathe...@in.ibm.com 2017-04-12 00:42 EDT--- Tested on guest kernel version. 4.10.0-19-generic and issue is fixed, though it takes quite (~ few secs) time, that would be different item. #uname -a Linux ubuntu 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux # virsh vcpucount virt-tests-vm1 --guest 1 # time virsh setvcpus virt-tests-vm1 255 --live real0m10.541s user0m0.013s sys 0m0.011s # virsh vcpucount virt-tests-vm1 --guest 226 # virsh vcpucount virt-tests-vm1 --guest 255---OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670315 Title: Ubuntu 17.04: Guest does not reflect all the cpus hotplugged Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Satheesh Rajendran - 2017-02-28 06:00:53 == ---Problem Description--- Guest does not reflect all the cpus hotplugged, Holpug vcpus using setvcpu with initial less number of cpus(1) to a greater cpus(~256), though setvcpu(libvirt) returns no error, guest does not reflect all cpus inside. Contact Information = sathe...@in.ibm.com ---uname output--- Linux ltc-test-ci1 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:45:11 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = power 8 ppc64le ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Start the guest(Ubuntu 17.04) with 1 current vcpu and 255 maxvcpus ... 255 ... # lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):1 On-line CPU(s) list: 0 Thread(s) per core:1 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported Hypervisor vendor: KVM Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0 2.# time virsh setvcpus virt-tests-vm1 255 --live --config real0m4.460s user0m0.012s sys 0m0.000s root@ltc-test-ci1:/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper# echo $? 0 3. Check inside the guest after some time (10-15 mins) ( dmesg of guest shows all the RTAS(255) events,but the guest showed only 90 vcpus(it consistent around ~ 100 always). root@ubuntu:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):97 On-line CPU(s) list: 0-96 Thread(s) per core:1 Core(s) per socket:97 Socket(s): 1 NUMA node(s): 1 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported Hypervisor vendor: KVM Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-96 root@ubuntu:~# tail /proc/cpuinfo processor : 96 cpu : POWER8E (raw), altivec supported clock : 3425.00MHz revision : 2.1 (pvr 004b 0201) timebase : 51200 platform : pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) Userspace tool common name: libvirt, qemu The userspace tool has the following bit modes: both Userspace rpm: qemu-kvm 1:2.8+dfsg- 2ubuntu1 ppc64el,ii libvirt-bin 2.5.0-3ubuntu2ppc64el Userspace tool obtained from project website: na Guest Details: #cat /etc/os-release |grep VERSION= VERSION="17.04 (Zesty Zapus)" # uname -a Linux ubuntu 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:~# dpkg -l |grep rtas ii librtas-dev2.0.0-2 ppc64el userspace RTAS library development files ii librtas2 2.0.0-2 ppc64el userspace RTAS library ii librtasevent-dev 2.0.0-2 ppc64el RTAS events library development files ii librtasevent2 2.0.0-2 ppc64el RTAS events library ii ppc64-diag 2.7.1-6 ppc64el Platform error log analysis tool and rtas_errd daemon *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application.
[Kernel-packages] [Bug 1680502] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860529/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860533/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860528/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860539/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860530/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860534/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860538/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860527/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860535/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860532/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860531/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860537/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860536/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arlie 2507 F pulseaudio /dev/snd/controlC0: arlie 2507 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 InstallationDate: Installed on 2012-04-26 (1811 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: System76, Inc. Wild Dog Performance NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 dmi.board.name: DH77KC dmi.board.vendor: Intel Corporation dmi.board.version: AAG39641-400 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: WilP9 dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: dmi.product.name: Wild Dog Performance dmi.product.version: wilp9 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04
apport information ** Tags added: apport-collected xenial ** Description changed: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. - I'm going to hard reboot the system now. I can then gather identifying - info. If I have time this AM before work, I'll check for standard things - you want in all bugs, and add them. (Right now I'm posting from my Mac - laptop ;-)) + I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: arlie 2507 F pulseaudio + /dev/snd/controlC0: arlie 2507 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=e206b01d-6cec-4b56-b469-25b106536f09 + InstallationDate: Installed on 2012-04-26 (1811 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) + MachineType: System76, Inc. Wild Dog Performance + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash + ProcVersionSignature: Ubuntu 4.4.0-72.93-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.157.8 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no + Tags: xenial + Uname: Linux 4.4.0-72-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2017-03-31 (11 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/24/2012 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825 + dmi.board.name: DH77KC + dmi.board.vendor: Intel Corporation + dmi.board.version: AAG39641-400 + dmi.chassis.type: 3 + dmi.chassis.vendor: System76, Inc. + dmi.chassis.version: WilP9 + dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9: + dmi.product.name: Wild Dog Performance + dmi.product.version: wilp9 + dmi.sys.vendor: System76, Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1680502/+attachment/4860526/+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/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a
[Kernel-packages] [Bug 1663414] Re: problem with wireless Network adapter after upgrading to 4.4.0-59
[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/1663414 Title: problem with wireless Network adapter after upgrading to 4.4.0-59 Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: after upgrading to linux 4.4.0-59, the RTL8188EUS 802.11n Wireless Network Adapter doen't work. but using 4.4.0-57 in the same computer it works normally ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 51.0.1+build2-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seba 1712 F pulseaudio /dev/snd/controlC1: seba 1712 F pulseaudio BuildID: 20170201180315 Channel: Unavailable CurrentDesktop: Unity Date: Thu Feb 9 19:55:56 2017 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-09-14 (148 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlxc4e984172267 proto static metric 600 169.254.0.0/16 dev wlxc4e984172267 scope link metric 1000 192.168.1.0/24 dev wlxc4e984172267 proto kernel scope link src 192.168.1.46 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201180315 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81H3-M4 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/13/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.name: H81H3-M4 dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1663414] Re: problem with wireless Network adapter after upgrading to 4.4.0-59
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) 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/1663414 Title: problem with wireless Network adapter after upgrading to 4.4.0-59 Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: after upgrading to linux 4.4.0-59, the RTL8188EUS 802.11n Wireless Network Adapter doen't work. but using 4.4.0-57 in the same computer it works normally ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 51.0.1+build2-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seba 1712 F pulseaudio /dev/snd/controlC1: seba 1712 F pulseaudio BuildID: 20170201180315 Channel: Unavailable CurrentDesktop: Unity Date: Thu Feb 9 19:55:56 2017 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-09-14 (148 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlxc4e984172267 proto static metric 600 169.254.0.0/16 dev wlxc4e984172267 scope link metric 1000 192.168.1.0/24 dev wlxc4e984172267 proto kernel scope link src 192.168.1.46 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=51.0.1/20170201180315 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81H3-M4 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/13/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.name: H81H3-M4 dmi.product.version: 1.0 dmi.sys.vendor: ECS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
Hi We have tried more tested and verified,so far still not resolved this issue and but we have workaround them commented "# set vt_handoff=vt.handoff=7"in grub.cfg ,It would can switch straight tty1.however,Do you known what's mean about gfxmode ? This issue always happened in PXE OS intaller function gfxmode { set gfxpayload="${1}" if [ "${1}" = "keep" ]; then # set vt_handoff=vt.handoff=7 else set vt_handoff= fi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645322] Re: Synaptics touchpad not detected in Clevo P650RS laptop
I have the same issue on a Metabox P650-RP (re-badged Clevo), Ubuntu 16.10, kernel 4.8.0-46. Adding i8042.reset to my kernel command line fixed it for me also. I'm currently upgrading to 17.04 so I'll see if the problem persists in the new kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1645322 Title: Synaptics touchpad not detected in Clevo P650RS laptop Status in linux package in Ubuntu: Incomplete Bug description: The laptop Clevo P650RS has a Synaptics touchpad but it is not detected by the kernel 4.8.0-27 on Ubuntu 16.10. There is no entry in /proc/bus/input/devices matching it. I installed Windows to check if it works at all, and it does. Windows identifies it as ACPI/SYN1219. WORKAROUND: Use kernel boot parameter: i8042.reset --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chfast27815 F pulseaudio /dev/snd/pcmC0D0p: chfast27815 F...m pulseaudio /dev/snd/controlC0: chfast27815 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=50613b4d-8b7f-4f75-b05a-193836f3ba1a InstallationDate: Installed on 2016-11-26 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Notebook P65_67RSRP NonfreeKernelModules: clevo_xsm_wmi nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67RSRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65_67RSRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656618] Re: Any key pressed opens shutdown dialog (Asus X205TA)
Blacklisting 'i2c-hid' does not resolve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656618 Title: Any key pressed opens shutdown dialog (Asus X205TA) Status in linux package in Ubuntu: Confirmed Bug description: After a fresh install of 16.10 on my Asus X205TA, any key pressed on the built-in keyboard brings up the shutdown dialog. The system works fine with a USB keyboard. The installed kernel was 4.8.0-34-generic. Booting with 4.8.0-22-generic, the keyboard works fine. Other users have confirmed the bug in Fedora and Tails (https://ubuntuforums.org/showthread.php?t=2254322&p=13594241#post13594241) and in 16.10 MATE (https://ubuntuforums.org/showthread.php?t=2254322&p=13594617#post13594617). --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 EcryptfsInUse: Yes Lsusb: Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X205TA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash intel_max.idle_cstate=1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-22-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/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA 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.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=94efdbb7-8cb5-442c-8a16-5fbe6fbf4959 InstallationDate: Installed on 2017-01-16 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X205TA Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mmcblk1p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X205TA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X205TA 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.:bvrX205TA.212:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX205TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX205TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X205TA dmi.product.version:
[Kernel-packages] [Bug 1680502] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1680502 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04
No pop-ups after today's hang, so that symptom is probably coincidental. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: New Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] Re: Hang after upgrade to 16.04
Assigning this to "linux" package. I have no evidence as to whether this is a kernel issue, or a case of user space processes with crazy priorities and tight loops etc. However in my experience (a) it takes a kernel person to distinguish the two (b) kernel people are more responsive than whoever monitors the no-package-assigned category. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680502 Title: Hang after upgrade to 16.04 Status in linux package in Ubuntu: New Bug description: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680502] [NEW] Hang after upgrade to 16.04
You have been subscribed to a public bug: Last week I upgraded from 12.04 LTS to 14.04 LTS and then immediately to 16.04 LTS. 12.04 was not entirely stable; something was crashing regularly, and the Ubuntu tools make it hard for a user to determine what. The upgrade went moderately well; I now get error messages during system startup (about an unnamed file not being found) and a couple of other bits of flakiness, but I counted it as a success and the system as functional. This morning I tried to wake up my screen, and nothing much happened. I then attempted to ssh to the ubuntu box from another system. This requested my password almost instantly, as normal - but then nothing else happened, and the connection eventually dropped. I conclude that IP and TCP are functional, and it's possible for some processes to respond, but not many. So it's not a complete kernel hang. (In particular, I'm seeing evidence that it's getting beyond things done at interrupt level.) I don't have any debugging aids installed, so I don't believe I can get a kernel crash dump, which is what I'd want if I were debugging this. I *can* potentially retrieve and attach logs, but you'll have to tell me which ones are relevant, and do so before they rollover. (Also, logging will have to be functioning; IIRC, there were syslog issues in 12.04, and while I'd implemented whatever fix was reccommended at the time, I haven't looked at my logs since the upgrade.) This is a desk top system originally from System 76 - i.e. built for linux - that's also running a bunch of server software (postfix, apache, ...) I was not (knowingly) running anythign unusual at the time - probably Unity, a few shells, firefox, maybe guncash and/or emacs - and all the usual demons. IIRC, I was not at the very latest versions of all software installed - some new versions ahd come out since I upgraded, and I was going to deal with installing them on the weekend. I'm going to hard reboot the system now. I can then gather identifying info. If I have time this AM before work, I'll check for standard things you want in all bugs, and add them. (Right now I'm posting from my Mac laptop ;-)) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Hang after upgrade to 16.04 https://bugs.launchpad.net/bugs/1680502 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1
Is there any intention of backporting either linux-aws or any of the NVMe bug fixes from linux-aws into linux-image-virtual-lts-xenial for Ubuntu 14.04 since they're both 4.4.0 kernels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1668129 Title: Amazon I3 Instance Buffer I/O error on dev nvme0n1 Status in linux package in Ubuntu: Triaged Status in linux-aws package in Ubuntu: Fix Committed Status in linux source package in Xenial: Triaged Status in linux-aws source package in Xenial: Fix Committed Bug description: On the AWS i3 instance class - when putting the new NVME storage disks under high IO load - seeing data corruption and errors in dmesg [ 662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912 [ 662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost async page write [ 662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost async page write [ 662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost async page write [ 662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost async page write [ 662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost async page write [ 662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost async page write [ 662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost async page write [ 662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost async page write [ 662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost async page write [ 662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost async page write [ 663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912 [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744 [ 1012.755396] buffer_io_error: 194552 callbacks suppressed [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async page write [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async page write [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async page write [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async page write [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async page write Able to replicate this with a bonnie++ stress test. bonnie++ -d /mnt/test/ -r 1000 Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 27 02:12 seq crw-rw 1 root audio 116, 33 Feb 27 02:12 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 Ec2AMI: ami-bc62b2aa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: i3.2xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial ec2-images Uname: Linux 4.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/12/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notific
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
96 successful deployments completed. No issues observed yet. Without this patch we saw 3 failures under 50 deployments, 1st failure at 19th iteration. We will run 2000 deployments in total in full testing. This is critical enough our development team believes the test kernel is valid and we should move forward integrating this 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/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1675188 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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. 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 1680680] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1680680 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680680 Title: Dell Z600 laptop will not suspend Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 What was expected to happen? I expected the laptop would suspend after selecting 'suspend' from the shutdown dialog. What happened instead? The screen went black and I was logged out, but the laptop did not suspend. Looking at dmesg, I found the following errors: [ 2229.003392] PM: Syncing filesystems ... done. [ 2229.018954] PM: Preparing system for sleep (mem) [ 2229.019765] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 2229.022084] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 2229.023408] PM: Suspending system (mem) [ 2229.023433] Suspending console(s) (use no_console_suspend to debug) [ 2229.024356] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -2 [ 2229.024366] PM: Device usb9 failed to suspend async: error -2 [ 2229.132836] PM: Some devices failed to suspend, or early wake event detected [ 2229.215860] PM: resume of devices complete after 83.019 msecs [ 2229.216299] PM: Finishing wakeup. [ 2229.216300] Restarting tasks ... done. [ 2229.292651] video LNXVIDEO:00: Restoring backlight state [ 2229.298616] PM: Syncing filesystems ... done. [ 2229.303267] PM: Preparing system for sleep (freeze) [ 2229.303522] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 2229.305692] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 2229.307033] PM: Suspending system (freeze) [ 2229.307035] Suspending console(s) (use no_console_suspend to debug) [ 2229.308819] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -2 [ 2229.308823] PM: Device usb9 failed to suspend async: error -2 [ 2229.416701] PM: Some devices failed to suspend, or early wake event detected [ 2229.416747] whci-hcd :0d:00.0-1: Unbalanced pm_runtime_enable! [ 2229.507852] PM: resume of devices complete after 91.145 msecs [ 2229.508267] PM: Finishing wakeup. [ 2229.508268] Restarting tasks ... done. And searching for Device usb9, I found the following bit of information: [7.140190] usb 3-1.3: new full-speed USB device number 5 using uhci_hcd [7.218134] whci-hcd :0d:00.0-1: reset timed out [7.218182] whci-hcd :0d:00.0-1: cannot get radio controller [7.227764] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [7.227767] kvm: disabled by bios [7.266789] intel_powerclamp: No package C-state available [7.270358] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [7.270360] kvm: disabled by bios [7.291281] usb 3-1.3: New USB device found, idVendor=413c, idProduct=8160 [7.291286] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [7.291289] usb 3-1.3: Product: Dell Wireless 365 Bluetooth Module [7.291291] usb 3-1.3: Manufacturer: Dell Computer Corp [7.335872] uwb_rc uwb0: new uwb radio controller on umc :0d:00.0-0 [7.337983] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [7.338762] intel_powerclamp: No package C-state available [7.348277] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [7.371534] whci-hcd :0d:00.0-1: Wireless host controller [7.371545] whci-hcd :0d:00.0-1: new USB bus registered, assigned bus number 9 [7.371564] whci-hcd :0d:00.0-1: irq 30, io base 0x [7.382524] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002 [7.382528] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [7.382530] usb usb9: Product: Wireless host controller [7.382533] usb usb9: Manufacturer: Linux 4.10.0-15-generic whci-hcd [7.382535] usb usb9: SerialNumber: whci To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You 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: New 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. 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 1680680] Re: Dell Z600 laptop will not suspend
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680680 Title: Dell Z600 laptop will not suspend Status in linux package in Ubuntu: New Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 What was expected to happen? I expected the laptop would suspend after selecting 'suspend' from the shutdown dialog. What happened instead? The screen went black and I was logged out, but the laptop did not suspend. Looking at dmesg, I found the following errors: [ 2229.003392] PM: Syncing filesystems ... done. [ 2229.018954] PM: Preparing system for sleep (mem) [ 2229.019765] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 2229.022084] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 2229.023408] PM: Suspending system (mem) [ 2229.023433] Suspending console(s) (use no_console_suspend to debug) [ 2229.024356] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -2 [ 2229.024366] PM: Device usb9 failed to suspend async: error -2 [ 2229.132836] PM: Some devices failed to suspend, or early wake event detected [ 2229.215860] PM: resume of devices complete after 83.019 msecs [ 2229.216299] PM: Finishing wakeup. [ 2229.216300] Restarting tasks ... done. [ 2229.292651] video LNXVIDEO:00: Restoring backlight state [ 2229.298616] PM: Syncing filesystems ... done. [ 2229.303267] PM: Preparing system for sleep (freeze) [ 2229.303522] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 2229.305692] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 2229.307033] PM: Suspending system (freeze) [ 2229.307035] Suspending console(s) (use no_console_suspend to debug) [ 2229.308819] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -2 [ 2229.308823] PM: Device usb9 failed to suspend async: error -2 [ 2229.416701] PM: Some devices failed to suspend, or early wake event detected [ 2229.416747] whci-hcd :0d:00.0-1: Unbalanced pm_runtime_enable! [ 2229.507852] PM: resume of devices complete after 91.145 msecs [ 2229.508267] PM: Finishing wakeup. [ 2229.508268] Restarting tasks ... done. And searching for Device usb9, I found the following bit of information: [7.140190] usb 3-1.3: new full-speed USB device number 5 using uhci_hcd [7.218134] whci-hcd :0d:00.0-1: reset timed out [7.218182] whci-hcd :0d:00.0-1: cannot get radio controller [7.227764] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [7.227767] kvm: disabled by bios [7.266789] intel_powerclamp: No package C-state available [7.270358] kvm: disable TXT in the BIOS or activate TXT before enabling KVM [7.270360] kvm: disabled by bios [7.291281] usb 3-1.3: New USB device found, idVendor=413c, idProduct=8160 [7.291286] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [7.291289] usb 3-1.3: Product: Dell Wireless 365 Bluetooth Module [7.291291] usb 3-1.3: Manufacturer: Dell Computer Corp [7.335872] uwb_rc uwb0: new uwb radio controller on umc :0d:00.0-0 [7.337983] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [7.338762] intel_powerclamp: No package C-state available [7.348277] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [7.371534] whci-hcd :0d:00.0-1: Wireless host controller [7.371545] whci-hcd :0d:00.0-1: new USB bus registered, assigned bus number 9 [7.371564] whci-hcd :0d:00.0-1: irq 30, io base 0x [7.382524] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002 [7.382528] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [7.382530] usb usb9: Product: Wireless host controller [7.382533] usb usb9: Manufacturer: Linux 4.10.0-15-generic whci-hcd [7.382535] usb usb9: SerialNumber: whci To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680276] Re: DRM for Via GPUs is missing
@sforshee Something should be in release notes and/or a text box in the installer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680276 Title: DRM for Via GPUs is missing Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: 17.04 Beta 2 (Zesty Zapus) amd64 Via PM800 chipset (S3 UniChrome Pro) Xorg.0.log: [25.194] (EE) CHROME(0): [drm] Failed to open DRM device for pci::01:00.0: No such file or directory … [25.469] (EE) AIGLX: reverting to software rendering ls /dev/dri/card0 ls: cannot access '/dev/dri/card0': No such file or directory ls /lib/modules/4.10.0-15-generic/kernel/drivers/gpu/drm/via/via.ko ls: cannot access '/lib/modules/4.10.0-15-generic/kernel/drivers/gpu/drm/via/via.ko': No such file or directory No DRM so no acceleration with Openchrome. This will make me and other Ubuntu 17.04 users with Via hardware sad (I'm guessing there's at least five of us). Makes for an annoying Ubuntu experience when browsing the web at nearly slide-show speeds while trying to find the correct drivers for our Nvidia and AMD cards. https://cgit.freedesktop.org/openchrome/drm-openchrome/ Not sure if it matters for the DRM module but Openchrome 0.6 has been released: https://lists.freedesktop.org/archives/openchrome- devel/2017-March/003232.html ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-15-generic 4.10.0-15.17 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 1313 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 5 19:02:03 2017 HibernationDevice: RESUME=UUID=34091ce2-a8c1-4a9f-9003-e91bf39fc4ae InstallationDate: Installed on 2017-04-05 (0 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321.1) IwConfig: enp0s18 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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: VIA Technologies, Inc. PM800-8237 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-15-generic root=UUID=f8e980c3-f382-4ec2-82b1-0b7c00b69932 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-15-generic N/A linux-backports-modules-4.10.0-15-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: PM800-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/21/2005:svnVIATechnologies,Inc.:pnPM800-8237:pvr:rvn:rnPM800-8237:rvr:cvn:ct3:cvr: dmi.product.name: PM800-8237 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675473] Re: Tablet pressure sensitivy doesn't xork for non-wacom tablet since the 16.04
I just tried the latest 4.11 rc 6 kernel, as well as older kernels down to 4.2. No result. This does not seem to be kernel based. Perhaps something to do with libinput? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675473 Title: Tablet pressure sensitivy doesn't xork for non-wacom tablet since the 16.04 Status in linux package in Ubuntu: Incomplete Bug description: I am unable to work with Ubuntu and Blender since one year, because since the 16.04 my Huion Tablet (GT-220 screen tablet) doesn't detect the pressure sensitivity and it worked before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
That version has 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/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install
Hi Kai-Heng. Then non-functional keys didn't register - attached is the dmesg log and the acpi_listen output. Only keys that did register were sleep [F1], Volume [F7] -> [F9] Regards, A?field.comment=Hi Kai-Heng. Then non-functional keys didn't register - attached is the dmesg log and the acpi_listen output. Only keys that did register were sleep [F1], Volume [F7] -> [F9] Regards, A ** Attachment added: "Bug No 1644919 - dmesg output 12 April for Kai-Heng" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+attachment/4860398/+files/Bug%20No%201644919%20-%20dmesg%20output%2012%20April%20for%20Kai-Heng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644919 Title: [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install Status in linux package in Ubuntu: Confirmed Bug description: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE P57 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB0B dmi.board.asset.tag: Default string dmi.board.name: P57 dmi.board.vendor: GIGABYTE dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: P57 dmi.product.version: Default string dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
I started a kernel bisect between v4.8.0-44 and v4.8.0-45. I built the first test kernel, up to the following commit: ac48b37537fd6218731af4108666239b2a578397 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1681904 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. Note, with this test kernel, you need to install both the linux-image and linux-image-extra .deb packages. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Yakkety) 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/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Re: XFS kernel modules still trying to flush device after it's been removed
It looks like your kernel is behind. The current lts-vivid kernel is: 3.19.0-82. You might want to apply the latest updates. Do you have a way to reproduce the bug? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Confirmed Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] 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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Confirmed Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
>Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels? @Joseph: yes, i have the issue with .45 and .46 while .44 is OK. i can boot all versions from grub. should i do the apport-collect and if so with what version booted? thanks for the very fast reply! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Re: XFS kernel modules still trying to flush device after it's been removed
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: New Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860358/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860354/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860355/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860353/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860351/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1681914 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860350/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Re: XFS kernel modules still trying to flush device after it's been removed
apport information ** Tags added: apport-collected trusty ** Description changed: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 15 2016 seq + crw-rw 1 root audio 116, 33 Sep 15 2016 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.11 + 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/lcx-swap00 + InstallationDate: Installed on 2016-02-22 (413 days ago) + InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: Dell Inc. PowerEdge R510 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M + ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-25-generic N/A + linux-backports-modules-3.19.0-25-generic N/A + linux-firmware 1.127.14 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 3.19.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/26/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.0 + dmi.board.name: 0DPRKF + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R510 + dmi.sys.vendor: Dell Inc. ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860348/+files/BootDmesg.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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix t
[Kernel-packages] [Bug 1681914] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860357/+files/UdevLog.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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860352/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860356/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860349/+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/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] [NEW] XFS kernel modules still trying to flush device after it's been removed
Public bug reported: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 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/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
This commit is already in Zesty from bug 1676635. I built a Xenial test kernel with this commit. It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1681893/ Can you test this kernel and see if it resolves this bug? ** Changed in: linux (Ubuntu Xenial) Importance: Medium => Critical ** Changed in: linux (Ubuntu Yakkety) Importance: Medium => Critical ** Changed in: linux (Ubuntu Zesty) Importance: Medium => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681909] Console log of successful dump capture after adding a time delay of 'sleep 30'
Default Comment by Bridge ** Attachment added: "Console log of successful dump capture after adding a time delay of 'sleep 30'" https://bugs.launchpad.net/bugs/1681909/+attachment/4860331/+files/kdump-with-sleep30-ssh.log ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => makedumpfile (Ubuntu) -- 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/1681909 Title: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21
[Kernel-packages] [Bug 1681909] [NEW] Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.
You have been subscribed to a public bug: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some errors in syslog ; auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question 114.15.239:/home/ubuntu/test IN SOA: failed-auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question 9.114.15.239:/home/ubuntu/test IN DS: failed-auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question 9.114.15.239:/home/ubuntu/test IN SOA: failed-auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question 9.114.15.239:/home/ubuntu/test IN A: failed-auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: Server 9.12.16.2 does not support DNSSEC, downgrading to non-DNSSEC mode. Mar 7 04:57:44 ltc-firep3 kdump-config: /root/.ssh/id_rsa failed to be sent to ubuntu
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
Thanks for the response. Do you recall what kernel version you were running with the kernel in comment #16? The current kernel in -proposed is 4.4.0-73.94. However, comment #16 was back in January. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
** Changed in: linux (Ubuntu Yakkety) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
There are not may commits between 4.8.0-44 and 4.8.0-45, so knowing the exact kernel when the regression started would be very helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1681904 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)
Does this regression happen with the Ubuntu 4.8.0-45 and newer kernels? If so we can bisect between 4.8.0-44 and 4.8.0-45. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** Tags added: kernel-da-key regression-update 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/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681904] [NEW] WLan not working after Kernel update (HWE)
Public bug reported: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681904 Title: WLan not working after Kernel update (HWE) Status in linux package in Ubuntu: New Bug description: After the update from 4.8.0.44 to newer versions, wifi stopped working. The controller is still found with `lshw -class network`, but wifi is not displayed in Network Manager. Hardware is Broadcom BCM4331 802.11a/b/g/n. What additional informations do you need to resolve this? - Apple MacBookPro10,2 from ~2012 elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac
Also we tried the workaround in comment #16 and blacklisting the mlx5_core module during the install and eth0 was not available. [ 16.198090] Atheros 8031 ethernet QCOM8070:00:04: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=QCOM8070:00:04, irq=-2) [ 16.198153] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 18.258062] 803x_aneg_done: SGMII link is not ok -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677297 Title: [Zesty] d-i: replace msm_emac with qcom_emac Status in linux package in Ubuntu: Incomplete Bug description: [Impact] We landed a patch to support msm_emac module in initrd for amberwing platforms. But the upstream driver has since been renamed to qcom_emac. This module is needed in d-i's initrd so that these nics can be used to d-i install the system. The driver already exists in the zesty kernel under drivers/net/ethernet/qualcomm/emac/ Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add qcom_emac to initrd, and change the module name to qcom_emac. [Test Case] D-I install zesty on amberwing platform and notice that DI does not recognize the onboard two port nic. [Regression Potential] At present this driver applies only to amberwing systems, any regression will be isolated to amberwing platforms. The over all risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680424] Re: linux-aws: 4.4.0-1014.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1680424 Title: linux-aws: 4.4.0-1014.23 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: 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 kernel-stable-master-bug: 1680416 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1680424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
** Tags added: kernel-da-key kernel-hyper-v xenial yakkety 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/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac
I did a D-I install on the qdf 2400 server with zesty + the patchset, using the Mellanox adapter (Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]). The qcom_emac driver is installed but the port (eth0) does not get an IP address without running dhclient -v. An IP address is assigned but not seen with the ifconfig command. I am able to ssh into that system using the assigned IP address, that I can only see from the output of the dhclient command. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677297 Title: [Zesty] d-i: replace msm_emac with qcom_emac Status in linux package in Ubuntu: Incomplete Bug description: [Impact] We landed a patch to support msm_emac module in initrd for amberwing platforms. But the upstream driver has since been renamed to qcom_emac. This module is needed in d-i's initrd so that these nics can be used to d-i install the system. The driver already exists in the zesty kernel under drivers/net/ethernet/qualcomm/emac/ Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add qcom_emac to initrd, and change the module name to qcom_emac. [Test Case] D-I install zesty on amberwing platform and notice that DI does not recognize the onboard two port nic. [Regression Potential] At present this driver applies only to amberwing systems, any regression will be isolated to amberwing platforms. The over all risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Zesty) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) 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/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681893] [NEW] [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
Public bug reported: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: Confirmed Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681893] Re: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg()
This commit should go into the 4.4, 4.8, and 4.10 kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681893 Title: [Hyper-V] hv: vmbus: Raise retry/wait limits in vmbus_post_msg() Status in linux package in Ubuntu: Confirmed Bug description: We've been hitting provisioning errors in Azure and narrowed down the cause to vmbus_post_msg timeouts. This upstream commit should alleviate this. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c0bb03924f1a80e7f65900e36c8e6b3dc167c5f8 DoS protection conditions were altered in WS2016 and now it's easy to get -EAGAIN returned from vmbus_post_msg() (e.g. when we try changing MTU on a netvsc device in a loop). All vmbus_post_msg() callers don't retry the operation and we usually end up with a non-functional device or crash. While host's DoS protection conditions are unknown to me my tests show that it can take up to 10 seconds before the message is sent so doing udelay() is not an option, we really need to sleep. Almost all vmbus_post_msg() callers are ready to sleep but there is one special case: vmbus_initiate_unload() which can be called from interrupt/NMI context and we can't sleep there. I'm also not sure about the lonely vmbus_send_tl_connect_request() which has no in-tree users but its external users are most likely waiting for the host to reply so sleeping there is also appropriate. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Cc: Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop
Xenial's 4.4.0-73.94 works for me too, after a reinstall. The laptop's an MSI U160, also with a Realtek 802.11n adapter with driver rtl8192cu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666421 Title: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic: Grub works, entering full disk encryption passphrase works, but when the desktop comes up mouse and keyboard (via USB) are dead and the desktop also. booting the PC without the stick attached works fine, but as soon as it is attached (see syslog) mouse, keyboard and the desktop itself are dead (checked by opening terminal and "watch date" - freezes, with desktop still visible). problem is resolved by booting former kernel 4.4.0-59-generic. syslog upon attaching stick --- Feb 21 07:17:02 orin kernel: [ 188.998338] usb 8-2: new high-speed USB device number 2 using xhci_hcd Feb 21 07:17:02 orin kernel: [ 189.129674] usb 8-2: New USB device found, idVendor=0bda, idProduct=8178 Feb 21 07:17:02 orin kernel: [ 189.129682] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 21 07:17:02 orin kernel: [ 189.129687] usb 8-2: Product: USB WLAN Feb 21 07:17:02 orin kernel: [ 189.129691] usb 8-2: Manufacturer: Realtek Feb 21 07:17:02 orin kernel: [ 189.129694] usb 8-2: SerialNumber: 00e04c01 Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: "/sys/devices/pci:00/:00:10.1/usb8/8-2" Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager... Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 'org.freedesktop.UDisks2' Feb 21 07:17:02 orin systemd[1]: Started Disk Manager. Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 on the system message bus Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive Feb 21 07:17:03 orin kernel: [ 190.200286] cfg80211: World regulatory domain updated: Feb 21 07:17:03 orin kernel: [ 190.200294] cfg80211: DFS Master region: unset Feb 21 07:17:03 orin kernel: [ 190.200297] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Feb 21 07:17:03 orin kernel: [ 190.200303] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200308] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200312] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200317] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200321] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200325] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Feb 21 07:17:03 orin kernel: [ 190.200329] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.200333] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Feb 21 07:17:03 orin kernel: [ 190.223081] rtl8192cu: Chip version 0x11 Feb 21 07:17:03 orin kernel: [ 190.625235] rtl8192cu: MAC address: 14:cc:20:10:43:98 Feb 21 07:17:03 orin kernel: [ 190.625241] rtl8192cu: Board Type 0 Feb 21 07:17:03 orin kernel: [ 190.626355] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 Feb 21 07:17:03 orin kernel: [ 190.626408] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7698] (wlan0): using nl80211 for WiFi device control Feb 21 07:17:03 orin kernel: [ 190.636625] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' Feb 21 07:17:03 orin kernel: [ 190.637211] usbcore: registered new interface driver rtl8192cu Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status... Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7780] device (wlan0): driver supports Access Point (AP) mode Feb 21 07:17:03 orin NetworkManager[1181]: [1487657823.7798] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4) Feb 21 07:17:03 orin k
[Kernel-packages] [Bug 1680424] Re: linux-aws: 4.4.0-1014.23 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-4.4.0-1014-dbgsym 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-cloud-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-headers-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-source-4.4.0 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-4.4.0-1014 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-4.4.0-1014-dbgsym 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-aws-tools-common 4.4.0-1014.23 - is in main instead of universe linux-cloud-tools-4.4.0-1014-aws 4.4.0-1014.23 - is in main instead of universe linux-headers-4.4.0-1014-aws 4.4.0-1014.23 - is in main instead of universe linux-image-4.4.0-1014-aws 4.4.0-1014.23 - is in main instead of universe linux-image-4.4.0-1014-aws-dbgsym 4.4.0-1014.23 - is in main instead of universe linux-tools-4.4.0-1014-aws 4.4.0-1014.23 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** 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 => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1680424 Title: linux-aws: 4.4.0-1014.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: 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 kernel-stable-master-bug: 1680416 phase: Uploaded To manage
[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Sure thing. I have been running with "nvme_core.default_ps_max_latency_us=250" and repo kernel for about 24 hours now without issue. Confirmed with nvme that APST is enabled. I will switch to "nvme_core.default_ps_max_latency_us=3000" later today or tomorrow. $ sudo nvme get-feature -f 0x0c -H /dev/nvme0 get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled $ uname -a Linux TEC-AJC2-U 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. $ sudo nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 ** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB512 B + 0 B BXV76D0Q ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajclayton 3305 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 09:42:38 2017 InstallationDate: Installed on 2012-09-08 (1665 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
Apport for 3.13 kernel, where lirc-sir works very well. ** Attachment added: "Apport with 3.13 kernel, where lirc works very well." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+attachment/4860299/+files/apport.lirc.5G3wSV.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Confirmed Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 Tags: trusty Uname: Linux 4.11.0-041100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860292/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Confirmed Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 Tags: trusty Uname: Linux 4.11.0-041100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
apport information ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 + --- + ApportVersion: 2.14.1-0ubuntu3.23 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + Package: lirc 0.9.0-0ubuntu5 + PackageArchitecture: amd64 + Tags: trusty + Uname: Linux 4.11.0-041100rc6-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860291/+files/Dependencies.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Confirmed Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39
[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
This issue goes away if I boot back into 3.13 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Confirmed Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860263/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482390] Re: ASUS UX305LA - Battery state not detected correctly
I got the same issue with Asus UX310UQ, Ubuntu 16.04 4.8.0-46-generic It's dual boot laptop and on Win10 everything is ok with battery status. Build in laptop diods indicates that it plugged in and fully charged. Output of my upower --dump: Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: вт, 11-кві-2017 18:33:38 +0300 (1907 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: вт, 11-кві-2017 19:03:38 +0300 (107 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 46,785 Wh energy-empty:0 Wh energy-full: 48,051 Wh energy-full-design: 48,336 Wh energy-rate: 0 W voltage: 11,4 V percentage: 97% capacity:99,4104% technology: lithium-ion icon-name: 'battery-full-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: вт, 11-кві-2017 18:33:38 +0300 (1907 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 46,785 Wh energy-full: 48,051 Wh energy-rate: 0 W percentage: 97% icon-name: 'battery-full-symbolic' Daemon: daemon-version: 0.99.4 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482390 Title: ASUS UX305LA - Battery state not detected correctly Status in linux package in Ubuntu: Triaged Bug description: Whether the AC adapter is connected or not, the battery is always detected as discharging: When AC adapter is present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0% AC adapter : online $ sudo acpitool -B Battery #1 : present Remaining capacity : 54027 mWh, 100.0% Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 0 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS When AC adapter is not present: $ sudo acpitool -a -b Battery #1 : Discharging, 100.0%, 04:19:49 AC adapter : off-line $ sudo acpitool -B Battery #1 : present Remaining capacity : 54005 mWh, 100.0%, 04:28:31 Design capacity: 56041 mWh Last full capacity : 53507 mWh, 95.48% of design capacity Capacity loss : 4.522% Present rate : 12067 mW Charging state : Discharging Battery type : Li-ion Model number : ASUS System information: $ sudo dmidecode # dmidecode 2.12 # SMBIOS entry point at 0xace2a898 SMBIOS 2.8 present. 27 structures occupying 2154 bytes. Table at 0xAC7C6000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: UX305LA.202 Release Date: 04/16/2015 Address: 0xF Runtime Size: 64 kB ROM Size: 6464 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.6 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx UUID: xxx Wake-up Type: Power Switch SKU Number: ASUS-NotebookSKU Family: UX Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: UX305LA Version: 1.0 Serial Number: xxx
[Kernel-packages] [Bug 1680328] Re: Broken PowerNV PCI hotplug driver - Patch backporting to zesty
** 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/1680328 Title: Broken PowerNV PCI hotplug driver - Patch backporting to zesty Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Problem Description = Broken PowerNV PCI hotplug driver - Patch backporting to zesty Machine Type = Supermicro P8DNU ---Debugger--- A debugger was configured, however the system did not enter into the debugger ---Steps to Reproduce--- On ubuntu (zesty), the NVMe adapter hotplug functionality is broken. After check, there are 3 more patches needed. There are 3 upstream patches needed by ubuntu.zesty are: [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d7d55536c6cd1f80295b6d7483ad0587b148bde4 ... which reads "drivers/pci/hotplug: Handle presence detection change properly" [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d0c424971f70501ec0a0364117b9934db039c9cc ... which reads "drivers/pci/hotplug: Fix initial state for empty slot" [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=454593e54cac126a0f49d4b65f90a5e518c51404 ... which reads "drivers/pci/hotplug: Mask PDC interrupt if required" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860262/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860258/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860257/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860253/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] modified.conffile..etc.lirc.lircd.conf.txt
apport information ** Attachment added: "modified.conffile..etc.lirc.lircd.conf.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860267/+files/modified.conffile..etc.lirc.lircd.conf.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] modified.conffile..etc.lirc.hardware.conf.txt
apport information ** Attachment added: "modified.conffile..etc.lirc.hardware.conf.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860266/+files/modified.conffile..etc.lirc.hardware.conf.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860264/+files/UdevLog.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860265/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860261/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860259/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860260/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860256/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860255/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860254/+files/Dependencies.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860252/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860251/+files/BootDmesg.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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
apport information ** Tags added: apport-collected staging ** Description changed: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 + --- + ApportVersion: 2.14.1-0ubuntu3.23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: dugi 10933 F pulseaudio + /dev/snd/controlC0: dugi 10933 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: lirc 0.9.0-0ubuntu5 + PackageArchitecture: amd64 + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw + 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: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + StagingDrivers: lirc_sir + Tags: trusty staging trusty + Uname: Linux 4.4.0-72-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 07/11/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.60 + dmi.board.name: FM2A75 Pro4-M + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M:rvr: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. + mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 + mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1681838/+attachment/4860250/+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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Incomplete Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeSta