[Kernel-packages] [Bug 1659750] [NEW] Wifi does not work
Public bug reported: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wifi xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659750 Title: Wifi does not work Status in linux package in Ubuntu: New Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659750] 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/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Confirmed Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90
Zesty is not affected as the fixup was in v4.9-rc2. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659654 Title: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Bug description: klibc is failing to build on arm64 in yakkety because of a change in unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and 4.8.0-36.38: gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -I/<>/linux/arch/arm64/include -Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os -march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o usr/klibc/ syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def In file included from /<>/linux/include/asm/unistd.h:19:0, from usr/klibc/SYSCALLS.def:13: /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style comments are not allowed in ISO C90 //__SYSCALL(__NR_pkey_get, sys_pkey_get) ^ /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will be reported only once per input file) https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893 We should reasonably expect the headers in linux-libc-dev to maximally-conformant C headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659654] Re: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90
This looks to be introduced by a60f7b69d92c0142c80a30d669a76b617b7f6879 in v4.9-rc1 and fixed up by 71757904efadefdf5505712f675218ce59483c5d in v4.9-rc2. The former was backported into Yakkety to resolve bug #1591804. Will submit the latter for SRU into Yakkety. ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659654 Title: regression in linux-libc-dev in yakkety: C++ style comments are not allowed in ISO C90 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Bug description: klibc is failing to build on arm64 in yakkety because of a change in unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and 4.8.0-36.38: gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/arm64 -Iusr/include/arch/arm64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -I/<>/linux/arch/arm64/include -Ilinux/arch/arm64/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-exceptions -mgeneral-regs-only -g -Os -march=armv8-a -mtune=generic -W -Wall -Wno-sign-compare -Wno-unused-parameter -I/<>/usr/klibc/syscalls -D__ASSEMBLY__ -ansi -x c -E -o usr/klibc/ syscalls/SYSCALLS.i usr/klibc/SYSCALLS.def In file included from /<>/linux/include/asm/unistd.h:19:0, from usr/klibc/SYSCALLS.def:13: /<>/linux/include/asm-generic/unistd.h:734:1: error: C++ style comments are not allowed in ISO C90 //__SYSCALL(__NR_pkey_get, sys_pkey_get) ^ /<>/linux/include/asm-generic/unistd.h:734:1: error: (this will be reported only once per input file) https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu3.1/+build/11926893 We should reasonably expect the headers in linux-libc-dev to maximally-conformant C headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653361] Re: [Asus E502SA] Suspend/resume triggers random hang
4.10-rc5 still suffered from this problem but today I did "git pull" on development kernel and built it and it seems that the problem is now gone. If it is so, then this should be fixed in 4.10-rc6 when it comes out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653361 Title: [Asus E502SA] Suspend/resume triggers random hang Status in linux package in Ubuntu: Incomplete Bug description: Resuming from suspend hangs the computer. This doesn't happen with Windows 10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamse 1839 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 31 18:01:35 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d46d5e40-bd0f-41a5-87bb-f4f470f7b4d6 InstallationDate: Installed on 2016-12-14 (17 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 006: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E502SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=17457b58-fc63-470b-a916-2eedb0dbd58e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E502SA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E502SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE502SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE502SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE502SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E502SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659767] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1659767 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/1659767 Title: NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM Status in linux package in Ubuntu: Incomplete Bug description: NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM 00:08.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) if onboard memory 2GB or 6GB or 8GB - work well: eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15104012 errors:212 dropped:3 overruns:212 frame:0 TX packets:4541749 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1082003467 (1.0 GB) TX bytes:44325680612 (44.3 GB) if memory 4GB - then no incoming packets. eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0 KB) TX bytes:912 (1.0 KB) ubuntu 16.04.1 LTS last updates, x64 Version: ASUS M2N-E ACPI BIOS Revision 5001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659767] [NEW] NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM
Public bug reported: NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM 00:08.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) if onboard memory 2GB or 6GB or 8GB - work well: eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15104012 errors:212 dropped:3 overruns:212 frame:0 TX packets:4541749 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1082003467 (1.0 GB) TX bytes:44325680612 (44.3 GB) if memory 4GB - then no incoming packets. eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0 KB) TX bytes:912 (1.0 KB) ubuntu 16.04.1 LTS last updates, x64 Version: ASUS M2N-E ACPI BIOS Revision 5001 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659767 Title: NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM Status in linux package in Ubuntu: Incomplete Bug description: NVIDIA MCP55 Eth (rev a2) not work with 4GB of RAM 00:08.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) if onboard memory 2GB or 6GB or 8GB - work well: eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15104012 errors:212 dropped:3 overruns:212 frame:0 TX packets:4541749 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1082003467 (1.0 GB) TX bytes:44325680612 (44.3 GB) if memory 4GB - then no incoming packets. eth0 Link encap:Ethernet HWaddr 00:18:f3:xx:xx:xx inet addr:192.168.x.x Bcast:192.168.x.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:45 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
[Kernel-packages] [Bug 1659750] Re: Wifi does not work
I also tried to boot from live USB, both 14.04.1 and 16.04.1 and same thing. I could not switch wireless on by "Fn + F5" in Linux https://support.lenovo.com/fi/en/documents/migr-63140 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659750 Title: Wifi does not work Status in linux package in Ubuntu: Confirmed Bug description: Network manager tells "device not ready". Restarting network manager does not help. Wifi failed to work occasionally before, but now it does not work at all. Hardware may be broken. At least it is as for wired network, I suppose. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1623 F pulseaudio CurrentDesktop: XFCE Date: Fri Jan 27 10:03:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (273 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
v4.7.5 passed v4.7.6 failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620089] Re: REGRESSION: Laptop hangs during second time it suspends
I don't know about Xenial, because I upgraded to Yakkety in the mean time. However, also on Yakkety, the bug still happens. $ uname -a Linux hellorobot 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy linux-image-generic linux-image-generic: Installed: 4.8.0.34.43 Candidate: 4.8.0.34.43 Version table: *** 4.8.0.34.43 500 500 http://nl.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status 4.8.0.22.31 500 500 http://nl.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages ** Tags added: 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/1620089 Title: REGRESSION: Laptop hangs during second time it suspends Status in linux package in Ubuntu: Incomplete Bug description: On Kubuntu 15.10 I had a problem with the suspend functionality on my laptop. The second time it suspends it would hang, and a hard reset was necessary to resolve the problem. After the update to 16.04, the problem was resolved (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552216) I updated my laptop using the xenial-updates repository. After the upgrade to linux 4.4.0-31, the suspend issue returned. I have also tried later updates (4.4.0-34 and 4.4.0-36), but the issue is also present in those versions. I therefore still use 4.4.0-28. I tried bisecting, but after a few iterations it messed up my boot partition, and after repairing that, I no longer took the time to finish the bisection. (see https://launchpad.net/ubuntu/+source/linux/4.4.0-31.50 for changelog) I have a short bit (but not complete work) of the git bisect log: $ git bisect log # bad: [2a1e175b928aefed1fd3c90c98e845f764fa8684] UBUNTU: Ubuntu-4.4.0-31.50 # good: [a6409cad137621e2b43d9f49c757fbc996539e85] UBUNTU: Ubuntu-4.4.0-28.47 git bisect start 'Ubuntu-4.4.0-31.50' 'Ubuntu-4.4.0-28.47' # bad: [44d66d94ed3e6e2434b06af7180a441cbf2b9f83] UBUNTU: Ubuntu-4.4.0-29.48 git bisect bad 44d66d94ed3e6e2434b06af7180a441cbf2b9f83 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan9230 F pulseaudio Date: Sun Sep 4 19:42:54 2016 HibernationDevice: RESUME=UUID=321acbbf-9a6a-4825-8f47-a89d56536272 InstallationDate: Installed on 2016-02-03 (214 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:57eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro nogpumanager quiet splash pci=noaer 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.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.160 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A4 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** Description changed: + == SRU REQUEST [Xenial, Yakkety, Zesty] == + Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. + + == Fix == + + Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses + the issue. The patch has been accepted into the upstream queue for + 4.11. + + == Test Case == + + run 10 times: + sudo stress-ng --fstat 128 -t 60 -v + + Without the fix, it will hang, with the fix there is no hang or USB + error messages. + + == Regression Potential == + + This only quirks a specific AMI virtual keyboard and mouse into a poll + mode, so it touches one device. Futhermore, the poll mode shouldn't + affect operation; it just makes the URB handling less efficient. ** Description changed: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for - 4.11. + 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: == SRU REQUEST [Xenial, Yakkety, Zesty] == Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. == Fix == Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://www.spinics.net/lists/linux-usb/msg152977.html == Test Case == run 10 times: sudo stress-ng --fstat 128 -t 60 -v Without the fix, it will hang, with the fix there is no hang or USB error messages. == Regression Potential == This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1652132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659812] [NEW] subprocess installed post-removal script returned error exit status 1
Public bug reported: i cant download application from software center ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1659812 Title: subprocess installed post-removal script returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: i cant download application from software center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1659812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659813] [NEW] subprocess installed post-removal script returned error exit status 1
Public bug reported: i cant download application from software center ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1659813 Title: subprocess installed post-removal script returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: i cant download application from software center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1659813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Changed in: qemu (Ubuntu) Status: New => Triaged ** Changed in: qemu (Ubuntu Xenial) Status: New => Triaged ** Changed in: qemu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Triaged Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz
[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
Hi Dennis or anyone who can help, So I tried to fix my disconnecting wifi (ubuntu 16.04 on xps 9360) with sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true After reboot the wifi option was no longer visibe, ls /lib/firmware/ath10k/QCA6174/hw3.0 showed both board.bin and board-2.bin so I did sudo mv /lib/firmware/ath10k/QCA6174/hw3.0/board.bin /lib/firmware/ath10k/QCA6174/hw3.0/board.bin.bak now ls /lib/firmware/ath10k/QCA6174/hw3.0 shows board-2.bin and board.bin.bak but still no wifi option on the after reboot? Anyone have any suggestions on what I need to do? I would rather have disconnecting wifi than no wifi at all, also I'm completely new to linux and have no idea what I am doing so please be gentle! Ok so also tried sudo mv /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin /lib/firmware/ath10k/QCA6174/hw3.0/board.bin.bak which seems to have done nothing but eliminate board-2.bin >< heeelp pleeease -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773]
Re: [Kernel-packages] [Bug 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns
On Thu, Jan 26, 2017 at 10:42:44PM -, Jonathan Calmels wrote: > Thinking more about it, this might be due to the lack of > CAP_DAC_OVERRIDE so I guess I need this too right? Yes, since you removed write permissions from the directory you're not able to write to it without capabilities. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659087 Title: open(2) returns EOVERFLOW within tmpfs+userns Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when creating a file in tmpfs with user namespace enabled. This issue wasn't present in 4.4.0-47 and has probably been introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964 Step to reproduce: $ unshare -r -U -m /bin/bash # mount -t tmpfs tmpfs /mnt # echo $$ 2354 In another terminal: $ sudo nsenter -t 2354 -m # touch /mnt/foo touch: cannot touch '/mnt/foo': Value too large for defined data type Note that we are not joining the user namespace when creating the file but we would expect `touch' to succeed and create the file with an inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655476 Title: linux: 3.13.0-108.155 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-108.155 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Hi, I am having the exact same issues on a PC with 18GB ram!! kernel 4.4.0-59-generic Please can this be fixed as soon as possible with a release of the next kernel update. Its killing processes such as firefox and virtualbox for no good reason while only 4gb is in use really. Hope this can be fixed soon. its becoming worse as time passes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Triaged Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing 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/1655476 Title: linux: 3.13.0-108.155 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug is for tracking the 3.13.0-108.155 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
You could try updating your kernel - I'm on 4.4.0-57. 4.8.x also works for me. My board-2.bin is 337204 bytes. My firmware-4.bin is 733784 bytes. This combination def works for me. Dowloaded from https://github.com/kvalo/ath10k- firmware/tree/master/QCA6174/hw3.0 .The firmware-5.bin under the 4.4 directory doesn't work for me. I have another board-2.bin (not sure where I got this other version) which is 271412 bytes - it doesn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
The patchset[1] for bug "LP #1655842" has been submitted on Jan 24th 2017 and acked by the kernel team on the same day[2]. The patch should be part of the following kernel release cycle : cycle: 27-Jan through 18-Feb[3] 27-Jan Last day for kernel commits for this cycle 30-Jan - 04-Feb Kernel prep week. 05-Feb - 17-Feb Bug verification & Regression testing.. 20-Feb Release to -updates. [1] - "Xenial PATCH 00/11] Fixes OOM for LP #1655842" [2] - "ACK: [Xenial PATCH 00/11] Fixes OOM for LP #1655842" [3] - https://wiki.ubuntu.com/KernelTeam/Newsletter - Eric ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Additional note : Applied in master-next on Jan 26th 2017[2] [1] - "APPLIED: [Xenial PATCH 00/11] Fixes OOM for LP #1655842" - Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10
Hi Joe, The test kernels with the commits are looking fine, I was able to successfully trigger and complete a kdump over NMI. Tested Xenial and Yakkety on WS2016 and WS2012R2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630924 Title: Kdump through NMI SMP and single core not working on Ubuntu16.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: 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: During some tests I've encountered an issue with kdump through NMI SMP and single core. After kdump configuration, when I trigger the crash through an NMI call from the host, the VM will panic, however it will not write the vmcore dump files and neither reboot. REPRO STEPS: 1. configure kdump - crashkernel=512M-:384M /boot/grub/grub.cfg - USE_KDUMP=1 /etc/default/kdump-tools 2. after configuration reboot the VM 3. check kdump status - cat /sys/kernel/kexec_* - service kdump-tools status 4. configure NMI - sysctl -w kernel.unknown_nmi_panic=1 5. trigger a crash from host - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer -Force This case also applies to: -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic) -Ubuntu 16.04.1(kernel: 4.4.0-38-generic) -Ubuntu 14.04.5(kernel: 3.19.0-69-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659621] Re: Random freezes and reboots since last kernel update
> Does this bug go away if you boot back into the prior kernel version? I'm trying 4.4.0-58-lowlatency right now, the kernel I was using previously to the 4.4.0-62-lowlatency. After I test that one I'll try with the latest v4.4 as suggested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659621 Title: Random freezes and reboots since last kernel update Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: I noticed my Laptop () started to freeze and reboot randomly and checking the apt logs the date where this started matches a kernel update: Start-Date: 2017-01-22 18:09:20 Commandline: apt full-upgrade Requested-By: luca (1000) Install: linux-image-4.4.0-62-lowlatency:amd64 (4.4.0-62.83, automatic) Upgrade: linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83), linux-image-lowlatency:amd64 (4.4.0.59.62, 4.4.0.62.65), libapt-inst2.0:amd64 (1.2.18, 1.2.19), libsystemd0:amd64 (229-4ubuntu15, 229-4ubuntu16), libsystemd0:i386 (229-4ubuntu15, 229-4ubuntu16), apt:amd64 (1.2.18, 1.2.19), sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3), udev:amd64 (229-4ubuntu15, 229-4ubuntu16), libapt-pkg5.0:amd64 (1.2.18, 1.2.19), libudev1:amd64 (229-4ubuntu15, 229-4ubuntu16), libudev1:i386 (229-4ubuntu15, 229-4ubuntu16), docker-engine:amd64 (1.12.6-0~ubuntu-xenial, 1.13.0-0~ubuntu-xenial), firefox-locale-de:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), systemd-sysv:amd64 (229-4ubuntu15, 229-4ubuntu16), firefox-locale-en:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), systemd:amd64 (229-4ubuntu15, 229-4ubuntu16), mysql-common:amd64 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), apt-utils:amd64 (1.2.18, 1.2.19), libmysqlclient20:i386 (5.7.16-0ubuntu0.16.04.1, 5.7.17-0ubuntu0.16.04.1), firefox:amd64 (50.1.0+build2-0ubuntu0.16.04.1, 51.0+build2-0ubuntu0.16.04.1), apt-transport-https:amd64 (1.2.18, 1.2.19), linux-tools-common:amd64 (4.4.0-59.80, 4.4.0-62.83) Purge: linux-image-4.4.0-57-lowlatency:amd64 (4.4.0-57.78) End-Date: 2017-01-22 18:10:27 Looking at /var/log/kernel.log (attached fragment) I found a backtrace including the i915 module. Attached is the output from lspci and lshw. Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-62-lowlatency 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-62.83-lowlatency 4.4.40 Uname: Linux 4.4.0-62-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: luca 2999 F...m pulseaudio /dev/snd/controlC1: luca 2999 F pulseaudio /dev/snd/controlC0: luca 2999 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Thu Jan 26 18:59:53 2017 HibernationDevice: RESUME=UUID=841aac03-34a5-409e-a845-fdb0c6d7284a InstallationDate: Installed on 2015-11-12 (440 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20DT001TGE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-lowlatency root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-lowlatency N/A linux-backports-modules-4.4.0-62-lowlatency N/A linux-firmware 1.157.8 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-12-05 (52 days ago) dmi.bios.date: 08/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JDET54WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT001TGE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DT001TGE dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659889] [NEW] Acer Aspire E15 trackpad not properly detected
Public bug reported: xinput: Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ UNKNOWN id=12 [slave pointer (2)] cat /proc/bus/input/devices I: Bus=0003 Vendor=06cb Product=2970 Version=0111 N: Name="UNKNOWN" P: Phys=usb-:00:13.0-1.3/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb4/4-1/4-1.3/4-1.3:1.0/0003:06CB:2970.0002/input/input12 U: Uniq= H: Handlers=mouse1 event12 B: PROP=1 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 ** 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/1659889 Title: Acer Aspire E15 trackpad not properly detected Status in linux package in Ubuntu: New Bug description: xinput: Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ UNKNOWN id=12 [slave pointer (2)] cat /proc/bus/input/devices I: Bus=0003 Vendor=06cb Product=2970 Version=0111 N: Name="UNKNOWN" P: Phys=usb-:00:13.0-1.3/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb4/4-1/4-1.3/4-1.3:1.0/0003:06CB:2970.0002/input/input12 U: Uniq= H: Handlers=mouse1 event12 B: PROP=1 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659889] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1659889 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/1659889 Title: Acer Aspire E15 trackpad not properly detected Status in linux package in Ubuntu: Incomplete Bug description: xinput: Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ UNKNOWN id=12 [slave pointer (2)] cat /proc/bus/input/devices I: Bus=0003 Vendor=06cb Product=2970 Version=0111 N: Name="UNKNOWN" P: Phys=usb-:00:13.0-1.3/input0 S: Sysfs=/devices/pci:00/:00:13.0/usb4/4-1/4-1.3/4-1.3:1.0/0003:06CB:2970.0002/input/input12 U: Uniq= H: Handlers=mouse1 event12 B: PROP=1 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=2608003 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659905] [NEW] On include/linux/ftrace.h issue.
Public bug reported: On my kernel , i make some modigications on ordet to remove suppress error message from compiler. Run make Bellow is error message from compiler: CC init/init_task.o In file included from include/linux/init_task.h:7:0, from init/init_task.c:1: include/linux/ftrace.h:781:28: error: request for member ‘ret_stack’ in something not a structure or union #define INIT_FTRACE_GRAPH .ret_stack = NULL, ^ include/linux/init_task.h:253:2: note: in expansion of macro ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed make: *** [init] Error 2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2838 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 19:23:06 2017 InstallationDate: Installed on 2016-04-29 (273 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659905 Title: On include/linux/ftrace.h issue. Status in linux package in Ubuntu: Confirmed Bug description: On my kernel , i make some modigications on ordet to remove suppress error message from compiler. Run make Bellow is error message from compiler: CC init/init_task.o In file included from include/linux/init_task.h:7:0, from init/init_task.c:1: include/linux/ftrace.h:781:28: error: request for member ‘ret_stack’ in something not a structure or union #define INIT_FTRACE_GRAPH .ret_stack = NULL, ^ include/linux/init_task.h:253:2: note: in expansion of macro ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed make: *** [init] Error 2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2838 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 19:23:06 2017 InstallationDate: Installed on 2016-04-29 (273 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic
[Kernel-packages] [Bug 1608236] Re: Regression: S-video output does not work
Sorry the status was changed, wrong bug. Just to confirm, this bug does not exists with the Yakkety? If that is the case, there is another commit there that fixes this bug, since yakkety does in fact contain commit 14de6c44d. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1608236 Title: Regression: S-video output does not work Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Regression. S-video output can not be used. It works by 4.4.0-22-generic. xrandr tells on 4.4.0-31-generic: TV1 unknown connection (normal left inverted right x axis y axis) 848x480 50.00 + 640x480 50.00 + 1024x768 50.00 800x600 50.00 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1573 F pulseaudio CurrentDesktop: XFCE Date: Sun Jul 31 17:15:16 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (94 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 89224MG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=15cc1d62-fbc6-4ce3-bf32-e35c61a921cf ro RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/06 dmi.bios.vendor: LENOVO dmi.bios.version: 63ET13WW dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: LENOVO dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr63ET13WW:bd09/13/06:svnLENOVO:pn89224MG:pvr3000C200:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 89224MG dmi.product.version: 3000 C200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659905] 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/1659905 Title: On include/linux/ftrace.h issue. Status in linux package in Ubuntu: Confirmed Bug description: On my kernel , i make some modigications on ordet to remove suppress error message from compiler. Run make Bellow is error message from compiler: CC init/init_task.o In file included from include/linux/init_task.h:7:0, from init/init_task.c:1: include/linux/ftrace.h:781:28: error: request for member ‘ret_stack’ in something not a structure or union #define INIT_FTRACE_GRAPH .ret_stack = NULL, ^ include/linux/init_task.h:253:2: note: in expansion of macro ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed make: *** [init] Error 2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu2838 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 19:23:06 2017 InstallationDate: Installed on 2016-04-29 (273 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658255] Re: Kernel not enforcing module signatures under SecureBoot
Bah, was missing the linux-signed-generic-hwe-16.04-edge package. Once that was in place, secure boot enforcement works correctly. Not sure if that's the cause of Kees' issue as well. That said, making it more discoverable that (a) secure boot is not being enforced by the kernel, (b) why it's not being enforced, and (c) shouldn't a boot stack that's enforcing secure boot not permit an unsigned kernel to boot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658255 Title: Kernel not enforcing module signatures under SecureBoot Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: $ sudo mokutil --sbstate SecureBoot enabled $ cat /proc/sys/kernel/moksbstate_disabled 0 $ sudo insmod ./hello.ko $ echo $? 0 $ dmesg | grep Hello [00112.530866] Hello, world! $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature ~Module signature appended~ $ strings hello.ko | grep signature $ uname -r 4.8.0-34-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641593] Re: unable to enable iommu on HPE Proliant Gen9 server
** Description changed: I'm using MAAS to enable the following kernel flags on install/boot: iommu=pt intel_iommu=on in order to be able to passthrough SR-IOV VF functions to KVM guess; however when these options are enabled, the servers fail to install (see attached screenshot). The install eventually fails - it looks like the writes back to one of the disks starts to fail for some reason. Servers are targeted with Xenial and the release 4.4 kernel (no HWE). + + Here's the LSHW output from the system: + http://pastebin.ubuntu.com/23875929/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641593 Title: unable to enable iommu on HPE Proliant Gen9 server Status in linux package in Ubuntu: Incomplete Bug description: I'm using MAAS to enable the following kernel flags on install/boot: iommu=pt intel_iommu=on in order to be able to passthrough SR-IOV VF functions to KVM guess; however when these options are enabled, the servers fail to install (see attached screenshot). The install eventually fails - it looks like the writes back to one of the disks starts to fail for some reason. Servers are targeted with Xenial and the release 4.4 kernel (no HWE). Here's the LSHW output from the system: http://pastebin.ubuntu.com/23875929/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658255] Re: Kernel not enforcing module signatures under SecureBoot
Also, is there a reason there isn't at least recommends on the corresponding -signed packages for the kernel, to try to avoid this situation? (I realize adding a hard depends would make building/installing test kernels more difficult.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658255 Title: Kernel not enforcing module signatures under SecureBoot Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: $ sudo mokutil --sbstate SecureBoot enabled $ cat /proc/sys/kernel/moksbstate_disabled 0 $ sudo insmod ./hello.ko $ echo $? 0 $ dmesg | grep Hello [00112.530866] Hello, world! $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature ~Module signature appended~ $ strings hello.ko | grep signature $ uname -r 4.8.0-34-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
> hey @ddstreet I've just tried your kernel at > https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894 and it now shows > both disks for me. > Please let me know how we can get this moved along. Happy to test. It's already in -proposed, please see https://wiki.ubuntu.com/Testing/EnableProposed for details on how to use the proposed repository. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659918] 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/1659918 Title: On include/linux/init_task.h issue Status in linux package in Ubuntu: Confirmed Bug description: On my kernel , i make some modifications on order to remove suppress error message from compiler. Run make Bellow is error message from compiler: In file included from init/init_task.c:1:0: include/linux/init_task.h:258:2: error: initializer element is not constant INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:258:2: note: (near initialization for ‘init_task.mempolicy’) INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:260:2: error: expected ‘}’ before ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3463 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 20:15:09 2017 InstallationDate: Installed on 2016-04-29 (273 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
hey @ddstreet I've just tried your kernel at https://launchpad.net/~ddstreet/+archive/ubuntu/lp1626894 and it now shows both disks for me. Please let me know how we can get this moved along. Happy to test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659918] [NEW] On include/linux/init_task.h issue
Public bug reported: On my kernel , i make some modifications on order to remove suppress error message from compiler. Run make Bellow is error message from compiler: In file included from init/init_task.c:1:0: include/linux/init_task.h:258:2: error: initializer element is not constant INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:258:2: note: (near initialization for ‘init_task.mempolicy’) INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:260:2: error: expected ‘}’ before ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3463 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 20:15:09 2017 InstallationDate: Installed on 2016-04-29 (273 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659918 Title: On include/linux/init_task.h issue Status in linux package in Ubuntu: Confirmed Bug description: On my kernel , i make some modifications on order to remove suppress error message from compiler. Run make Bellow is error message from compiler: In file included from init/init_task.c:1:0: include/linux/init_task.h:258:2: error: initializer element is not constant INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:258:2: note: (near initialization for ‘init_task.mempolicy’) INIT_TRACE_IRQFLAGS \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ include/linux/init_task.h:260:2: error: expected ‘}’ before ‘INIT_FTRACE_GRAPH’ INIT_FTRACE_GRAPH \ ^ init/init_task.c:8:32: note: in expansion of macro ‘INIT_TASK’ struct task_struct init_task = INIT_TASK(init_task); ^ scripts/Makefile.build:291: recipe for target 'init/init_task.o' failed make[1]: *** [init/init_task.o] Error 1 Makefile:963: recipe for target 'init' failed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3463 F pulseaudio CurrentDesktop: MATE Date: Fri Jan 27 20:15:09 2017 InstallationDate:
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
I started a kernel bisect between v4.8-rc7 and v4.8-rc8. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: f887c21e214757e6b1b9dd65e396ee3e7cbb6b18 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1659340 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8
No need to test the 4.5-rc1 kernel. Because v4.4-wily is good, we can not bisect between 4.4 and 4.5-rc1. It also means that the bug was introduced by one of the 4.4 stable updates, or by an Ubuntu specific SAUCE patch. We should bisect between the 4.4 Ubuntu kernels. However, it would be good to also know if this bug was also introduced into Yakkey(16.10). Can you test the latest Yakkety kernel, which can be downloaded from: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11765356 With that kernel, you need to install both the linux-image and linux- image-extra .deb packages. For the Xenial bisect, the kernels we need to test are all available from: https://launchpad.net/ubuntu/xenial/+source/linux What we would need to do is test the kernels and find the earliest kernel that does not have the bug, then the first that does. Then we would bisect between those two versions to find the offending commit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656605 Title: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Today I did our first production 14.04 to 16.04 LTS server upgrade. I had done so a couple of times successfully on test server machines. Upon booting up on the 16.04 system/kernel, after the Grub screen the server console screen is completely blank. Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those hotkeys does toggle through the tty screens. There is no boot process logged to the server console screen. I did have the last 14.04 kernel yet installed, so selected that one from the Grub menu. Booting that 14.04 kernel, then server console display behaves normally. So I suspected perhaps a bum install of the 16.04 kernel. I used the following commands while booted to the 14.04 kernel to reinstall the 16.04 kernel: $ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic linux-image-generic $ sudo apt-get install linux-image-generic Same results booting the 16.04 kernel after those steps. Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8
Noted you want me to test the Yakkey(16.10) kernel specified. About the Xenial kernels... I am thinking to walk the version list back from 4.4.0-59 to land on one that does not have the error. Then post the last one that was working, and the first one with the noted defect. Does that sound like a plan to you, Joseph? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656605 Title: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Today I did our first production 14.04 to 16.04 LTS server upgrade. I had done so a couple of times successfully on test server machines. Upon booting up on the 16.04 system/kernel, after the Grub screen the server console screen is completely blank. Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those hotkeys does toggle through the tty screens. There is no boot process logged to the server console screen. I did have the last 14.04 kernel yet installed, so selected that one from the Grub menu. Booting that 14.04 kernel, then server console display behaves normally. So I suspected perhaps a bum install of the 16.04 kernel. I used the following commands while booted to the 14.04 kernel to reinstall the 16.04 kernel: $ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic linux-image-generic $ sudo apt-get install linux-image-generic Same results booting the 16.04 kernel after those steps. Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658255] Re: Kernel not enforcing module signatures under SecureBoot
... why aren't all the kernels just signed? Why does this need to be a separate package at all? I can confirm installing the -signed package fixes it for me. Where in the kernel source does this signature effect the output of /proc/sys/kernel/secure_boot, though? I can't find that... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658255 Title: Kernel not enforcing module signatures under SecureBoot Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: $ sudo mokutil --sbstate SecureBoot enabled $ cat /proc/sys/kernel/moksbstate_disabled 0 $ sudo insmod ./hello.ko $ echo $? 0 $ dmesg | grep Hello [00112.530866] Hello, world! $ strings /lib/modules/$(uname -r)/kernel/lib/test_module.ko | grep signature ~Module signature appended~ $ strings hello.ko | grep signature $ uname -r 4.8.0-34-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) 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/1658270 Title: Backport Dirty COW patch to prevent wineserver freeze Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Bug description: A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi apps freezing wineserver and leaving it unkillable: https://bugs.winehq.org/show_bug.cgi?id=41637 I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it is probably affected. A patch is available: https://lkml.org/lkml/2017/1/5/13 --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jhansonxi 2775 F pulseaudio /dev/snd/controlC2: jhansonxi 2775 F pulseaudio /dev/snd/controlC0: jhansonxi 2775 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/vg0-lv1 ro quiet nosplash ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout WifiSyslog: _MarkForUpload: True dmi.bios.date: 11/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
Hmm I tried that earlier today and thought it failed to boot, let me try -proposed again now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
v4.8-rc7-201701261200 passed When I installed this kernel with "sudo dpkg -i *.deb" it replaced the previously installed v4.8-rc7. Was that alright? Should I have uninstalled the previous v4.8-rc7 before I installed the new one? Or isn't it necessary? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
4.8.0-040800rc7-generic #201701261200 passed [on Lenovo 710S (KabyLake i5-7200)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
@slashd It sounds really strange to me that I should wait til 20-Feb for a fix for this bug while this is clearly a regression introduced with the latest kernel upgrade. Is there no way to speed things up to fix this regression. Currently we had to downgrade all our xenial systems to linux- image-4.4.0-57-generic to avoid this bug. Gaudenz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659956] 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/1659956 Title: NVRM: failed to register procfs! spamming syslog Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu Xenial 64-bit on a Dell M3800, which is one of those dual video card things (built-in Intel as well as an nvidia). I'm currently getting the following message spamming my syslog so much I'm starting to get warnings about my disk getting full: Jan 27 13:12:09 Pandora kernel: [17958.566812] [ cut here ] Jan 27 13:12:09 Pandora kernel: [17958.566831] WARNING: CPU: 5 PID: 30095 at /build/linux-EO9xOi/linux-4.4.0/fs/proc/generic.c:352 proc_register+0xe8/0x110() Jan 27 13:12:09 Pandora kernel: [17958.566834] proc_dir_entry 'driver/nvidia' already registered Jan 27 13:12:09 Pandora kernel: [17958.566835] Modules linked in: nvidia(POE+) scsi_transport_iscsi binfmt_misc veth rfcomm bnep xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge pci_stub stp vboxpci(OE) llc vboxnetadp(OE) vboxnetflt(OE) iptable_filter ip_tables x_tables bbswitch(OE) vboxdrv(OE) drbg ansi_cprng dm_crypt pn544_mei mei_phy pn544 hci nfc dell_wmi sparse_keymap mxm_wmi dell_laptop wl(POE) dcdbas dell_smm_hwmon btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev snd_hda_codec_hdmi media snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp hid_multitouch snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core snd_hwdep aesni_intel snd_pcm aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq joydev rtsx_pci_ms snd_seq_device serio_raw memstick snd_timer snd soundcore shpchp mei_me mei ie31200_edac edac_core lpc_ich acpi_als kfifo_buf int3403_thermal industrialio processor_thermal_device mac_hid wmi intel_soc_dts_iosf int3402_thermal dell_rbtn dell_smo8800 int3400_thermal int340x_thermal_zone acpi_thermal_rel kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 hid_generic usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci psmouse drm libahci rtsx_pci video fjes [last unloaded: nvidia] Jan 27 13:12:09 Pandora kernel: [17958.566964] CPU: 5 PID: 30095 Comm: modprobe Tainted: PW OE 4.4.0-59-generic #80-Ubuntu Jan 27 13:12:09 Pandora kernel: [17958.566967] Hardware name: Dell Inc. Dell Precision M3800/Dell Precision M3800, BIOS A09 01/08/2015 Jan 27 13:12:09 Pandora kernel: [17958.566968] 0286 b03cf1e6 88013f7efae8 813f7583 Jan 27 13:12:09 Pandora kernel: [17958.566970] 88013f7efb30 81cde3d8 88013f7efb20 810812d2 Jan 27 13:12:09 Pandora kernel: [17958.566973] 880434158280 88046f089c00 880118aae205 88046f089c38 Jan 27 13:12:09 Pandora kernel: [17958.566986] [] dump_stack+0x63/0x90 Jan 27 13:12:09 Pandora kernel: [17958.566999] [] warn_slowpath_fmt+0x5c/0x80 Jan 27 13:12:09 Pandora kernel: [17958.567010] [] proc_register+0xe8/0x110 Jan 27 13:12:09 Pandora kernel: [17958.567016] [] proc_mkdir_mode+0x13/0x20 Jan 27 13:12:09 Pandora kernel: [17958.567466] [] nvidia_init_module+0x2a3/0x7a0 [nvidia] Jan 27 13:12:09 Pandora kernel: [17958.567803] [] nvidia_frontend_init_module+0x51/0x84b [nvidia] Jan 27 13:12:09 Pandora kernel: [17958.567820] [] ? __vunmap+0x91/0xe0 Jan 27 13:12:09 Pandora kernel: [17958.567833] [] do_init_module+0x5f/0x1cf Jan 27 13:12:09 Pandora kernel: [17958.567843] [] ? __symbol_put+0x60/0x60 Jan 27 13:12:09 Pandora kernel: [17958.567855] [] SYSC_finit_module+0xb4/0xe0 Jan 27 13:12:09 Pandora kernel: [17958.567868] [] entry_SYSCALL_64_fastpath+0x16/0x71 Jan 27 13:12:09 Pandora kernel: [17958.567873] NVRM: failed to register procfs! Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: This may be due to a known Linux kernel bug. Please Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: see the README section on 64-bit BARs for additional Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: information. Jan 27 13:12:09 Pandora kernel: [17958.568189] NVRM: The NVIDIA probe routine failed for 1 device(s). Jan 27 13:12:09 Pandora kernel: [17958.568191] [drm] Module unloaded Jan 27 13:12:09 Pandora systemd-udevd[13501]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 27 13:12:09 Pandora systemd-udevd[13501]: Process '/usr/bin/nvidia-smi' failed with exit code 12. Jan 27 13:12:09 Pandora
[Kernel-packages] [Bug 1659956] [NEW] NVRM: failed to register procfs! spamming syslog
Public bug reported: Running Ubuntu Xenial 64-bit on a Dell M3800, which is one of those dual video card things (built-in Intel as well as an nvidia). I'm currently getting the following message spamming my syslog so much I'm starting to get warnings about my disk getting full: Jan 27 13:12:09 Pandora kernel: [17958.566812] [ cut here ] Jan 27 13:12:09 Pandora kernel: [17958.566831] WARNING: CPU: 5 PID: 30095 at /build/linux-EO9xOi/linux-4.4.0/fs/proc/generic.c:352 proc_register+0xe8/0x110() Jan 27 13:12:09 Pandora kernel: [17958.566834] proc_dir_entry 'driver/nvidia' already registered Jan 27 13:12:09 Pandora kernel: [17958.566835] Modules linked in: nvidia(POE+) scsi_transport_iscsi binfmt_misc veth rfcomm bnep xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge pci_stub stp vboxpci(OE) llc vboxnetadp(OE) vboxnetflt(OE) iptable_filter ip_tables x_tables bbswitch(OE) vboxdrv(OE) drbg ansi_cprng dm_crypt pn544_mei mei_phy pn544 hci nfc dell_wmi sparse_keymap mxm_wmi dell_laptop wl(POE) dcdbas dell_smm_hwmon btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev snd_hda_codec_hdmi media snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp hid_multitouch snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core snd_hwdep aesni_intel snd_pcm aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi input_leds snd_seq joydev rtsx_pci_ms snd_seq_device serio_raw memstick snd_timer snd soundcore shpchp mei_me mei ie31200_edac edac_core lpc_ich acpi_als kfifo_buf int3403_thermal industrialio processor_thermal_device mac_hid wmi intel_soc_dts_iosf int3402_thermal dell_rbtn dell_smo8800 int3400_thermal int340x_thermal_zone acpi_thermal_rel kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 hid_generic usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci psmouse drm libahci rtsx_pci video fjes [last unloaded: nvidia] Jan 27 13:12:09 Pandora kernel: [17958.566964] CPU: 5 PID: 30095 Comm: modprobe Tainted: PW OE 4.4.0-59-generic #80-Ubuntu Jan 27 13:12:09 Pandora kernel: [17958.566967] Hardware name: Dell Inc. Dell Precision M3800/Dell Precision M3800, BIOS A09 01/08/2015 Jan 27 13:12:09 Pandora kernel: [17958.566968] 0286 b03cf1e6 88013f7efae8 813f7583 Jan 27 13:12:09 Pandora kernel: [17958.566970] 88013f7efb30 81cde3d8 88013f7efb20 810812d2 Jan 27 13:12:09 Pandora kernel: [17958.566973] 880434158280 88046f089c00 880118aae205 88046f089c38 Jan 27 13:12:09 Pandora kernel: [17958.566986] [] dump_stack+0x63/0x90 Jan 27 13:12:09 Pandora kernel: [17958.566999] [] warn_slowpath_fmt+0x5c/0x80 Jan 27 13:12:09 Pandora kernel: [17958.567010] [] proc_register+0xe8/0x110 Jan 27 13:12:09 Pandora kernel: [17958.567016] [] proc_mkdir_mode+0x13/0x20 Jan 27 13:12:09 Pandora kernel: [17958.567466] [] nvidia_init_module+0x2a3/0x7a0 [nvidia] Jan 27 13:12:09 Pandora kernel: [17958.567803] [] nvidia_frontend_init_module+0x51/0x84b [nvidia] Jan 27 13:12:09 Pandora kernel: [17958.567820] [] ? __vunmap+0x91/0xe0 Jan 27 13:12:09 Pandora kernel: [17958.567833] [] do_init_module+0x5f/0x1cf Jan 27 13:12:09 Pandora kernel: [17958.567843] [] ? __symbol_put+0x60/0x60 Jan 27 13:12:09 Pandora kernel: [17958.567855] [] SYSC_finit_module+0xb4/0xe0 Jan 27 13:12:09 Pandora kernel: [17958.567868] [] entry_SYSCALL_64_fastpath+0x16/0x71 Jan 27 13:12:09 Pandora kernel: [17958.567873] NVRM: failed to register procfs! Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: This may be due to a known Linux kernel bug. Please Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: see the README section on 64-bit BARs for additional Jan 27 13:12:09 Pandora kernel: [17958.567953] NVRM: information. Jan 27 13:12:09 Pandora kernel: [17958.568189] NVRM: The NVIDIA probe routine failed for 1 device(s). Jan 27 13:12:09 Pandora kernel: [17958.568191] [drm] Module unloaded Jan 27 13:12:09 Pandora systemd-udevd[13501]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 27 13:12:09 Pandora systemd-udevd[13501]: Process '/usr/bin/nvidia-smi' failed with exit code 12. Jan 27 13:12:09 Pandora systemd-udevd[13501]: Process '/usr/bin/start-nvidia-persistenced' failed with exit code 127. Jan 27 13:12:09 Pandora kernel: [17958.650729] WARNING: CPU: 6 PID: 30103 at /build/linux-EO9xOi/linux-4.4.0/fs/proc/generic.c:352 proc_register+0xe8/0x110() Jan 27 13:12:09 Pandora kernel: [17958.650732] Modules linked in: nvidia(POE+) scsi_transport_iscsi binfmt_misc veth rfcomm bnep xt_CHECKSUM iptable_mangle xt_tcpudp
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
Just installed kernel 4.4.0-62-generic from -proposed and both drives are appearing with no problems in dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] WifiSyslog.txt
Default Comment by Bridge ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809898/+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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Triaged Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8
[Kernel-packages] [Bug 1510196] Re: OOM killer causes complete system freezes
Sorry, failed to include version information: Linux hostname 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii linux-image-3.13.0-107-generic3.13.0-107.154 amd64Linux kernel image for version 3.13.0 on 64 bit x86 SMP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510196 Title: OOM killer causes complete system freezes Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: A race condition in the Linux kernel randomly causes complete system freezes when the system or a cgroup runs out of memory and the OOM killer is invoked. I ran into this issue twice during the last 2 weeks (Ubuntu 14.04.3 LTS, kernel version 3.13.0-65.106), in my case it was an LXC cgroup running out of memory and not the system itself. The system log files did not show any errors, but there were repeating error messages on the system console (see attached screenshot). When searching for these error messages I found the following website that provides more information about the cause and a possible solution to fix it: https://community.nitrous.io/posts/stability-and-a-linux- oom-killer-bug I did not see any OOM killer related messages in the system logs at the time the freeze happened, but one of the LXC containers running on that server went out of memory exactly at that time, so I guess this must be related. I was not able to reproduce the error in a testing environment as it seems to be a race condition between several processes that does not occur every time. However, I have applied the 3 suggested commits for mm/oom_kill.c (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=0c740d0afc3bff0a097ad03a1c8df92757516f5c...4d4048be8a93769350efa31d2482a038b7de73d0) from kernel 3.14 to the current trusty kernel, built the patched kernel and it seems to work. Could this bugfix for the OOM killer be backported to the official trusty kernel? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 09:12 seq crw-rw 1 root audio 116, 33 Oct 23 09:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Oct 26 12:19:55 2015 HibernationDevice: RESUME=UUID=728105e7-2f6b-46fd-bf56-1bf67239adea IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro H8DGT PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic root=UUID=08db4f0e-59c5-4ffd-a34c-866e3fe126c5 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-66-generic N/A linux-backports-modules-3.13.0-66-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: H8DGT-HF dmi.board.vendor: Supermicro dmi.board.version: 1.21A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: SGI.COM dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd05/07/2013:svnSupermicro:pnH8DGT:pvr1234567890:rvnSupermicro:rnH8DGT-HF:rvr1.21A:cvnSGI.COM:ct17:cvr1234567890: dmi.product.name: H8DGT dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1510196] Re: OOM killer causes complete system freezes
We're also hitting it more often then not on several up to date 14.04.5 systems. (AWS c4.large instances running python scripts via supervisor.) About 1 OOM event in 3 fires successfully, kills the process and continues on. For the others, the console indicates an OOM kill but cpu/disk spikes and it becomes completely unresponsive. (Nothing is logged to disk.) What further information can we add to help get this resolved? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510196 Title: OOM killer causes complete system freezes Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: A race condition in the Linux kernel randomly causes complete system freezes when the system or a cgroup runs out of memory and the OOM killer is invoked. I ran into this issue twice during the last 2 weeks (Ubuntu 14.04.3 LTS, kernel version 3.13.0-65.106), in my case it was an LXC cgroup running out of memory and not the system itself. The system log files did not show any errors, but there were repeating error messages on the system console (see attached screenshot). When searching for these error messages I found the following website that provides more information about the cause and a possible solution to fix it: https://community.nitrous.io/posts/stability-and-a-linux- oom-killer-bug I did not see any OOM killer related messages in the system logs at the time the freeze happened, but one of the LXC containers running on that server went out of memory exactly at that time, so I guess this must be related. I was not able to reproduce the error in a testing environment as it seems to be a race condition between several processes that does not occur every time. However, I have applied the 3 suggested commits for mm/oom_kill.c (https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=0c740d0afc3bff0a097ad03a1c8df92757516f5c...4d4048be8a93769350efa31d2482a038b7de73d0) from kernel 3.14 to the current trusty kernel, built the patched kernel and it seems to work. Could this bugfix for the OOM killer be backported to the official trusty kernel? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 23 09:12 seq crw-rw 1 root audio 116, 33 Oct 23 09:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Oct 26 12:19:55 2015 HibernationDevice: RESUME=UUID=728105e7-2f6b-46fd-bf56-1bf67239adea IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro H8DGT PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic root=UUID=08db4f0e-59c5-4ffd-a34c-866e3fe126c5 ro nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-66-generic N/A linux-backports-modules-3.13.0-66-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: H8DGT-HF dmi.board.vendor: Supermicro dmi.board.version: 1.21A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: SGI.COM dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd05/07/2013:svnSupermicro:pnH8DGT:pvr1234567890:rvnSupermicro:rnH8DGT-HF:rvr1.21A:cvnSGI.COM:ct17:cvr1234567890: dmi.product.name: H8DGT dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] UdevDb.txt
Default Comment by Bridge ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809897/+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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Triaged Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To
[Kernel-packages] [Bug 1656112] nvram.gz
Default Comment by Bridge ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1656112/+attachment/4809899/+files/nvram.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Triaged Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
I built the next test kernel, up to the following commit: d0c1d15f5ed7f028d2c284b7fed7e73575d9c24d The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1659340 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658621] Re: Touchpad is not detected in Acer Aspire One AO756-2626
Thanks Joseph. The problem persists if I boot into 4.2.7 or into 4.10.0 Sorry for the delay - hectic week! Cheers, Josh ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658621 Title: Touchpad is not detected in Acer Aspire One AO756-2626 Status in linux package in Ubuntu: Confirmed Bug description: After most recent update to kernel, my touchpad is not recognised and does not appear as an input device in cat /proc/bus/input/devices An external USB mouse is working correctly (cursor, buttons and scroll wheel) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 1777 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 23 09:12:32 2017 HibernationDevice: RESUME=UUID=9aee6652-765c-4b42-9ffd-9370a0d95ca1 MachineType: Acer AO756 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=a872dd55-2af1-4efd-b447-ec434bff8dcf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-30 (146 days ago) dmi.bios.date: 11/06/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.08 dmi.modalias: dmi:bvnAcer:bvrV2.08:bd11/06/2012:svnAcer:pnAO756:pvrV2.08:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.08: dmi.product.name: AO756 dmi.product.version: V2.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566987] Re: No internet connection through WLAN although connected to network
** Changed in: linux (Ubuntu) Importance: Undecided => 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/1566987 Title: No internet connection through WLAN although connected to network Status in linux package in Ubuntu: Confirmed Bug description: In a fresh install of Kubuntu 16.04 on a ThinkPad t460s, I can connect wireless to the local WLAN, but I don't have an internet connection. A ping to the router doesn't work in that case. After some minutes, the connection usually (but not always) works. A LAN connection through the same router works, too. It seems that the problem doesn't occur in every WLAN, but in my home network (using an O2 box 6431) it always does. The problem is reproducible with a Kubuntu Live CD/USB. The following steps did not solve the problem: - Reconnect to WLAN - Using kernel 4.6 or 4.7 - Restarting NetworkManager and networking service - Disable IPv6 - Factory reset of the o2 box - Restart of the o2 box (sometimes it helps temporarily) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-04 (294 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Package: linux (not installed) Tags: xenial Uname: Linux 4.7.4-040704-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Merge proposal linked: https://code.launchpad.net/~leftyfb/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/315823 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Triaged Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: Triaged Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage
[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
I downloaded, put into /lib/firmware/ath10k/QCA6174/hw3.0 and rebooted but it is still not working :/ any more ideas on what it could be? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 27.759534] ath10k_pci :07:00.0: could not suspend target (-11) [
[Kernel-packages] [Bug 1659381] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-28_03-37-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/modoc__4.8.0-35.37~16.04.1__2017-01-28_04-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_03-48-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 1
tests ran: 33, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_04-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_05-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_03-17-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659381] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_03-15-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659381] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/onza__4.8.0-37.39__2017-01-28_04-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659381] Re: linux: 4.8.0-37.39 -proposed tracker
** Also affects: linux (Ubuntu Yakkety) 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/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_03-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_05-52-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_05-54-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] dwalin (amd64) - tests ran: 34, failed: 4
tests ran: 34, failed: 4; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/dwalin__4.8.0-35.37~16.04.1__2017-01-28_03-37-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onza__4.8.0-35.37~16.04.1__2017-01-28_04-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onza (i386) - tests ran: 4, failed: 1
tests ran: 4, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onza__4.8.0-35.37~16.04.1__2017-01-28_06-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
[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/1625381 Title: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu Status in linux package in Ubuntu: Expired Bug description: On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu there is a crash that randomly happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onibi (amd64) - tests ran: 34, failed: 4
tests ran: 34, failed: 4; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onibi__4.8.0-35.37~16.04.1__2017-01-28_03-59-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] modoc (ppc64el) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/modoc__4.8.0-35.37~16.04.1__2017-01-28_04-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 16, failed: 4
tests ran: 16, failed: 4; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_05-19-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onza (amd64) - tests ran: 34, failed: 4
tests ran: 34, failed: 4; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onza__4.8.0-35.37~16.04.1__2017-01-28_05-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659381] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-37.39-generic/modoc__4.8.0-37.39__2017-01-28_03-44-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 2
tests ran: 4, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-28_04-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onza__4.8.0-35.37~16.04.1__2017-01-28_04-29-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] dwalin (amd64) - tests ran: 36, failed: 0
tests ran: 36, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/dwalin__4.8.0-35.37~16.04.1__2017-01-28_05-03-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642044] onibi (i386) - tests ran: 4, failed: 0
tests ran: 4, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-35.37~16.04.1-generic/onibi__4.8.0-35.37~16.04.1__2017-01-28_05-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642044 Title: linux: 4.9.0-11.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-6.7 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1642044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
