[Kernel-packages] [Bug 1655123] Re: Kernel 4.10 stalls on restart
Journal of errors can be seen is this bug #1656489 for the same installation. Sorry for sending info from the non-sudoer account. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
** Description changed: The following log comes from the installer syslog file. Since at least - Dec.16th a message is present in all variants of Ubuntu on startup. - Since then, in BIOS mode, all installers have opened in try Ubuntu. + Dec.16th a message is present in all variants of Ubuntu on startup + (ubiquity). Since then, in BIOS mode, all installers have opened in try + Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog - … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… - I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. - --- + --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) 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. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently
[Kernel-packages] [Bug 1656489] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1656489/+attachment/4804160/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity Status in linux package in Ubuntu: Confirmed Bug description: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) 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-journ
[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
Journal from admin account. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity Status in linux package in Ubuntu: Confirmed Bug description: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) 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 insuf
[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
apport information ** Description changed: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) 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. Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nopasswdlogin _MarkForUpl
[Kernel-packages] [Bug 1656489] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1656489/+attachment/4804158/+files/ProcEnviron.txt ** 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/1656489 Title: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity Status in linux package in Ubuntu: Confirmed Bug description: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from ot
[Kernel-packages] [Bug 1656489] [NEW] AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity
Public bug reported: The following log comes from the installer syslog file. Since at least Dec.16th a message is present in all variants of Ubuntu on startup. Since then, in BIOS mode, all installers have opened in try Ubuntu. There is no incidence on the installation except for xubuntu. In the Xu installer, the skin is light pink. This bug is not shown in the System Log and belongs to ubiquity. This is a fresh install of 17.04 on an HP desktop. 20170111 build Visible message on startup in the installer (all of them): [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 As seen from Try Ubuntu : /var/log/syslog … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0 Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512 Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0 Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives memory: 32K (b41ba000 - b41c2000) Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 entries in 132 pages Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting physical 1 to logical package 0 Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2 Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core perfctr, AMD PMU driver. Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width: 48 Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers: 6 Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 7fff Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events: 0 Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 003f Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration: Jan 13 18:19:25 ubuntu kernel: [0.185155] node #0, CPUs: #1 Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1 Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.187463] #2<3>[0.187735] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2 Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.190129] #3<3>[0.190398] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3 Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0 Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors activated (20761.91 BogoMIPS)… I had never seen this message in Zesty nor in Yakkety before Dec. 16th. This bug is not present in Xenial Xerus. Will be waiting for a correction in Ubiquity. Thanks in advance! Log files of this machine are shown in bug # 1655123 and were given about 2 hours ago. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-11 (2 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111) 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. Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nopasswdlogin _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected bios mode ubiquity zesty ** Tags added: apport
[Kernel-packages] [Bug 1641280] Re: Issues on include/linux/aer.h
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1641280
Title:
Issues on include/linux/aer.h
Status in linux package in Ubuntu:
Expired
Bug description:
Inline declaration is used here to supress warnings message from compiler,
and is already exported as module wich is bad.
As example on pci_enable_pcie_error_reporting
1. removed any reference from include/linux/aer.h because is already exported.
2. int pci_enable_pcie_error_reporting(struct pci_dev *dev)
{
#if defined(CONFIG_PCIEAER)
if (pcie_aer_get_firmware_first(dev))
return -EIO;
if (!pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ERR))
return -EIO;
return pcie_capability_set_word(dev, PCI_EXP_DEVCTL,
PCI_EXP_AER_FLAGS);
#else
return -EINVAL;
#endif
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-47-generic 4.4.0-47.68
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: pax
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: asu2510 F pulseaudio
CurrentDesktop: MATE
Date: Sat Nov 12 10:05:40 2016
InstallationDate: Installed on 2016-04-29 (196 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-47-generic
root=/dev/mapper/192--168--0--108--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-47-generic N/A
linux-backports-modules-4.4.0-47-generic N/A
linux-firmware1.157.4
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
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/1641280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640926] Re: Touchpad doesn't work after upgrading kernel
[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/1640926 Title: Touchpad doesn't work after upgrading kernel Status in linux package in Ubuntu: Expired Bug description: [Dell Latitude E5440] Touchpad doesn't work after upgrading generic kernel from 4.4.0-45 to 4.4.0-47 x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641317] Re: Multiple issues on include/linux/audit.h
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641317 Title: Multiple issues on include/linux/audit.h Status in linux package in Ubuntu: Expired Bug description: Declaring inline here is used to supress warnings and very bad ,errors from compiler. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: pax ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asu3140 F pulseaudio CurrentDesktop: MATE Date: Sat Nov 12 16:36:43 2016 InstallationDate: Installed on 2016-04-29 (197 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-47-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 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/1641317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen
** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635447 Title: Upgraded or Live USB 16.10 hangs at boot up blank purple screen Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: My HP dm3z-2000 laptop works out of box for everything with Ubuntu 16.04, but fails to boot up after upgraded to 16.10. The upgrading went smooth itself. Laptop still can boot up with the latest 4.4 kernel of 16.04 which I did a regular update/upgrade before 16.10 release upgrade. Then I tried to boot with 16.10 Live USB and got same result. It also can boot up with kernel 4.8 if "acpi=off" parameter in place, but it takes long time to boot up. Everything seems fine after logged in and Unity 8 session works too. I couldn't get any log files since the system won't boot up, Ctrl+Alt+F1 does nothing. I can only see some messages in text boot mode, so I took a screen shot with my phone and attached here. Let me know how to get more details. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renm 2918 F pulseaudio /dev/snd/controlC1: renm 2918 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc InstallationDate: Installed on 2016-10-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1482 dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm3t Notebook PC dmi.product.version: 048620241F0011032 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen
@Joseph, I've installed v4.10-rc3 via Ukuu and my laptop boots up successfully. ~$ uname -a Linux chengdu 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Everything seems work normal, even though I noticed some message about b43, but the WIFI works fine too. ~$ dmesg | grep b43 [ 21.933153] Support for cores revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try b43.allhwsupport=1 [ 21.933350] b43: probe of bcma0:1 failed with error -524 Thank you for your help. ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Confirmed ** 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/1635447 Title: Upgraded or Live USB 16.10 hangs at boot up blank purple screen Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: My HP dm3z-2000 laptop works out of box for everything with Ubuntu 16.04, but fails to boot up after upgraded to 16.10. The upgrading went smooth itself. Laptop still can boot up with the latest 4.4 kernel of 16.04 which I did a regular update/upgrade before 16.10 release upgrade. Then I tried to boot with 16.10 Live USB and got same result. It also can boot up with kernel 4.8 if "acpi=off" parameter in place, but it takes long time to boot up. Everything seems fine after logged in and Unity 8 session works too. I couldn't get any log files since the system won't boot up, Ctrl+Alt+F1 does nothing. I can only see some messages in text boot mode, so I took a screen shot with my phone and attached here. Let me know how to get more details. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renm 2918 F pulseaudio /dev/snd/controlC1: renm 2918 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc InstallationDate: Installed on 2016-10-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1482 dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm3t Notebook PC dmi.product.version: 048620241F0011032 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_03-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655123] Re: Kernel 4.10 stalls on restart
The bug is also present in bios mode alongside rs1. CKT 4.10.0-1.3 stalls on first restart and magic key works to restart again. As in UEFI mode the HDD is noisy, too noisy to keep it on board. Grub was OK for this test. That ends this bug report. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeS
[Kernel-packages] [Bug 1655123] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804138/+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/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 _MarkForUp
[Kernel-packages] [Bug 1655123] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804131/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 _MarkForUplo
[Kernel-packages] [Bug 1655123] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804136/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804134/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804135/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804130/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804129/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804137/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 _Ma
[Kernel-packages] [Bug 1655123] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804132/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 _MarkForUplo
[Kernel-packages] [Bug 1655123] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1655123/+attachment/4804133/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655123 Title: Kernel 4.10 stalls on restart Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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
[Kernel-packages] [Bug 1655123] Re: Kernel 4.10 stalls on restart
apport information ** Description changed: For rc2 and rc3, the machine stalls on first restart only (no tty) and runs OK after (no shutdown problems). Same result when removing the lowest Kernel (all of them). Canonical Kernel permanently stalls on restart but runs OK. Plus, the boot sequence passes by the Grub menu under 4.10.0-0 (not dual-boot, UEFI). Since last night, suspend mode won’t wake-up under rc3 (no tty). Kernel 4.9 stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic. FYI, for a couple of months now, Gnome Software refuses to install custom kernel. 20170107 build. --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.9.1-040901-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc2-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zz 1890 F pulseaudio /dev/snd/controlC0: zz 1890 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) IwConfig: enp1s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: HP 24-b019 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3 RelatedPackageVersions: linux-restricted-modules-4.10.0-1-generic N/A linux-backports-modules-4.10.0-1-generic N/A linux-firmware1.162 RfKill: Tags: zesty Uname: Linux 4.10.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/25/2016 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: 8CC6351M4W dmi.board.name: 81B8 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.asset.tag: 8CC6351M4W dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.deferred.probe: 0 dmi.modalias: dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr: dmi.product.name: 24-b019 dmi.sys.vendor: HP --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109) Package: linux (not installed) Tags: zesty Uname: Linux 4.10.0-041000rc3-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 --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test 2454 F pulseaudio /dev/snd/controlC0: test 2454 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=fc87eaaa-07c4-4916-9cbd-4a3cb592b160 InstallationDate: Installed on 2017-01-11 (0
[Kernel-packages] [Bug 1656084] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-lowlatency/onza__4.4.0-60.81__2017-01-14_02-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] onza (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_02-26-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
I've tested this with kernel 4.10-rc3 in a local VirtualBox VM (Ubuntu
Server 16.04), with the same fstab error as above, and am able to
confirm most of the symptoms described by the reporter.
When attempting to 'mount -a', it presents the expected "wrong
filesystem type" error, but doesn't render the system unresponsive.
Upon reboot, however, it drops into a maintenance console without
presenting an error about a failed mount attempt. Consequently, the
server would be unreachable for maintenance via SSH.
'journalctl -xb' provides a log that contains an error about the failed
mount attempt, but doesn't point to it as the reason for dropping into a
maintenance terminal, and it isn't the last thing logged.
After fixing fstab (which requires physical access) and rebooting
('reboot' from the maintenance console), GRUB does still have a
countdown, but it starts around 10 seconds, instead of 3 seconds (~3
seconds is the default for Ubuntu Server). Otherwise, at this point,
the system is able to boot up automatically, without issue.
After rebooting a second time (from the normal BASH prompt), the GRUB
countdown is back to ~3 seconds, and the system boots normally
(automatically), from there.
Thanks, again, for helping to resolve this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1463120
Title:
Failure to boot if fstab disk mounts fail
Status in linux package in Ubuntu:
Confirmed
Bug description:
I found this on my main 15.04 desktop but have reproduced it in a VM:
1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that
matters).
2. Add a bogus entry to /etc/fstab, eg:
/dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0
Note that /mnd/sdd1 exists but /dev/sdd1 does not
3. Reboot
Expected: Failure to mount /dev/sdd1 reported and option to boot without
mounting it
Actual: System appears to hang, although it will eventually present a root
terminal (with no indication of the cause of the problem). It appears to hang
prior to switching graphical mode, with the result that any warnings/errors
that are present on all boots but invisible because the screen clears before
they're seen become visible for the first time incorrectly suggesting they are
the cause of the problem.
Removing (or commenting out) the problematic entries and rebooting
allows the system to boot.
HOWEVER: The grub boot menu now appears and any pre-existing menu
timeout and default action seems to have been lost; it's now necessary
to select a boot option on each boot. This may be a separate bug (or
feature?).
My actual case: I have external drives permanently connected via USB, however
the USB card appears to have failed hence the drives are not accessible. With
no clues (and being unfamiliar to systemd) working out why the system wouldn't
boot was a tough job.
---
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mark 1382 F pulseaudio
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f
InstallationDate: Installed on 2015-06-08 (4 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic
root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
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-3.19.0-20-generic N/A
linux-backports-modules-3.19.0-20-generic N/A
linux-firmware 1.143.1
RfKill:
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
Looking at the file Christopher linked to earlier states this: "Organization: Intel Open Source Technology Center The Baytrail SOC has a built-in feature to demote core and module C6 to shallower idle states. Based on work in the Android copy of the Linux kernel tree, this feature was disabled starting in Linux-3.17-rc1:" ...So that looks promising as that is the exact thing we found in this bug report early on. Kernel 3.17 was the kernel i started getting huge freezes on, and when originally we were going through the bisecting rc1 was the one we had stopped at. So cool to see someone else has confirmed that portion. ...now to see if i can figure all this stuff Christopher wants me to do. Christopher i'm going to be honest and say that your really bad at explaining stuff since you just post links that are somewhat technical. I think i can figure it out, but my brain doesn't compute as fast as it used to. Right now i gather that i need to just edit my grub on bootup and test the intel_idle.max_cstate=1 parameter. (not sure if that will remain on future bootups or if that is persistent and will remain). Then if that works well i test the debug patch and script. (not sure if i need to disable intel_idle.max_cstate=1 when i do this). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz WORKAROUND: Use out-of-tree patch from https://bugzilla.kernel.org/show_bug.cgi?id=109051 . Patch file: https://bugzilla.kernel.org/attachment.cgi?id=247621 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
Christopher, the latest kernels don't freeze as much as the older ones. Do you want me to go back to an older kernel that froze up a lot to test the intel_idle.max_cstate=1 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz WORKAROUND: Use out-of-tree patch from https://bugzilla.kernel.org/show_bug.cgi?id=109051 . Patch file: https://bugzilla.kernel.org/attachment.cgi?id=247621 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea
Okay i have just removed Vincent's patched kernel. I will try and proceed and test Christopher's request to follow his steps to test his stuff. Vincent i will add that your patch seemed to work well, though i did have it lock up once. Only once that i can remember though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1575467 Title: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts- utopic-vy2yyy/linux-lts- utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_ready+0x126/0x170 [i915]() Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: After upgrading from stock Ubuntu 14.04 to 16.04 my laptop consistently freezes up and is unresponsive to keyboard or mouse. The only way is to do a hard shutdown. I'm usually in a browser when this happens, and often watching a video or two. It seems to happen more often in Google Chrome than Firefox, but it happens with both. It has happened at least once with no videos loaded. I haven’t observed it freeze / hang when I’m not in a browser, but that's mainly what i use my laptop for, so that's where most of my time is spent. Call trace: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz WORKAROUND: Use out-of-tree patch from https://bugzilla.kernel.org/show_bug.cgi?id=109051 . Patch file: https://bugzilla.kernel.org/attachment.cgi?id=247621 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrew 1949 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020 InstallationDate: Installed on 2015-08-08 (263 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Inspiron 3451 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0H4MK6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3451 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] onza (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/onza__4.4.0-60.81__2017-01-14_01-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/ms10-35-mcdivittB0-kernel__4.4.0-60.81__2017-01-14_01-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] modoc (ppc64el) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-60.81-generic/modoc__4.4.0-60.81__2017-01-14_02-06-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
I also tried to enable hibernation, same issue with NVME drives using hibernation as when using suspend. Skylake truly is a mess on Linux :/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] Re: linux: 4.4.0-60.81 -proposed tracker
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/kernel01__4.4.0-59.80__2017-01-14_01-36-00/results-index.html ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-60.81 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 -- derivative-trackers-created: true phase: Uploaded + kernel-stable-phase-changed:Saturday, 14. January 2017 01:33 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-60.81 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 - kernel-stable-phase-changed:Saturday, 14. January 2017 01:33 UTC - kernel-stable-phase:Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] s2lp3 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/s2lp3__4.4.0-59.80__2017-01-14_01-36-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/1656084 Title: linux: 4.4.0-60.81 -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 Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
As I suspected, issue is still present with the 4.10 kernels. Tried it on a separate clean install using 16.10 upgrading the kernel to v4.10-rc3 mainline This warning is present for 4.10 as well as for older kernels on the Alienware 15 R2 update-initramfs: Generating /boot/initrd.img-4.10.0-041000rc3-generic W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-041000rc3-generic /boot/vmlinuz-4.10.0-041000rc3-generic uname -a Linux starbase 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] Re: linux: 4.4.0-60.81 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -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: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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 -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651520] Re: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state
Christopher, *-rc versions are the release Candidates, once I installed it (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5) to check the same bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641152) in November and ended up without WiFi. I can't work on *-rc. The bug reproduced after the idle state, laptop lid closing or waking up from the sleeping mode with frequency about once per ~20-30 such actions. The probability seems to be higher when there are more opened windows and external monitor is plugging. In fact, the last 2 issues appeared on plugging the external monitor after the sleep mode. However the bug sometimes (about twice during 4 months) reproduced even on pure laptop without any external devices. I think that you don't have many reports about this bug only because the reporting should be done manually. Moreover, it's extremely hard for an ordinary user to perform such reporting when the UI is totally broken and apport-collect doesn't always success to report even if it was called (as nico mentioned, and I also had the same issue with the apport-collect). --- Info about the kernels: [a few older kernels (< 4.4.0-50) have the UI scrambling issue] -4.4.0-51 - OK: UI scrambling has never occurred, but sometimes (when UI scrambling occurs on another kernels) on this kernel system windows become non-sensitive to the mouse clicks: shortcuts on the desktop are clicked behind the foreground window instead of it. This can be fixed by closing and reopening the window (which does not help on another kernels with the UI scrambling issue). On this kernel the windows can always be moved using the title panel (the top bar of the window) even when the remained part of the [foreground] window is not sensitive (transparent for the mouse clicks). -4.4.0-53, 4.4.0-57, 4.4.0-59 - UI scrambling issue - 4.9.3-040903 - under the evaluation. It survived the stress testing without any issues: intentional subsequent lid closing, laptop suspending and external monitor plugging (up to 20 times). Now is under the "working" testing as my default working kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651520 Title: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state Status in linux package in Ubuntu: Incomplete Bug description: Text in Unity windows becomes a total mess after suspending and waking up Ubuntu 16.04. Text content in most of system and native windows are scrambled including terminal, nautilus, native apps EXCEPT Java apps (browsers and LibreOffice work fine). I had this issue multiple times, but it is not always reproducible. This bug occurs in linux-image-generic 4.4.0.53. It does not appear with linux-image-extra-4.4.0-51-generic 4.4.0-51.72 amd64. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lav2950 F pulseaudio /dev/snd/controlC0: lav2950 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-25 (801 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20A8S28400 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 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 Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-11 (114 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET39WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A8S28400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A8S28400 dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.
[Kernel-packages] [Bug 1655100] Re: NVME devices and Network devices disappears upon suspend
** Description changed: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME - devices and the network devices area gone. + devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-4.8.0-22-generic N/A - linux-backports-modules-4.8.0-22-generic N/A - linux-firmware1.161 + linux-restricted-modules-4.8.0-22-generic N/A + linux-backports-modules-4.8.0-22-generic N/A + linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
(New kernel is still compiling...) I just did a test with a fully-patched, newly spun-up Ubuntu Server 14.04 AWS instance, and the behavior seems to be present with kernel 3.13.0-107. I can't verify all of the symptoms described by the reporter, because I don't have physical access; but I get "connection refused" when trying to SSH into it, after making an intentionally-bad edit to /etc/fstab. For completeness, this is the bad edit I made: /home/ubuntu/test.img /mnt ext4 defaults 0 0 The file referenced was created with: dd if=/dev/zero of=/home/ubuntu/test.img bs=1M count=20 When attempting to mount this file from the command-line, it produces a "wrong filesystem type" error, as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 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-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651520] Re: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state
Artem V L, the latest mainline kernel is presently 4.10-rc3 (not 4.9.x). Despite this, regarding your hardware specifically, how often would it be reproducible on average when using the Ubuntu kernel (ex. linux- image-generic 4.4.0.53)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651520 Title: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state Status in linux package in Ubuntu: Incomplete Bug description: Text in Unity windows becomes a total mess after suspending and waking up Ubuntu 16.04. Text content in most of system and native windows are scrambled including terminal, nautilus, native apps EXCEPT Java apps (browsers and LibreOffice work fine). I had this issue multiple times, but it is not always reproducible. This bug occurs in linux-image-generic 4.4.0.53. It does not appear with linux-image-extra-4.4.0-51-generic 4.4.0-51.72 amd64. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lav2950 F pulseaudio /dev/snd/controlC0: lav2950 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-25 (801 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20A8S28400 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 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 Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-11 (114 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET39WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A8S28400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A8S28400 dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.13.0-031300 kernel boots fine, 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/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656084] Re: linux: 4.4.0-60.81 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) ** Description changed: This bug is for tracking the 4.4.0-60.81 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Thursday, 12. January 2017 20:16 UTC - -- swm properties -- derivative-trackers-created: true phase: Packaging + kernel-stable-phase-changed:Friday, 13. January 2017 23:32 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-60.81 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 -- derivative-trackers-created: true - phase: Packaging - kernel-stable-phase-changed:Friday, 13. January 2017 23:32 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656084 Title: linux: 4.4.0-60.81 -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-60.81 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 -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1656084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
Thanks for your attention on this bug, Joseph. I'm compiling the new kernel, now, and will let you know as soon as I have a test result. As far as I know, all 16.04 kernel versions exhibit this problem; but I haven't done any testing on Ubuntu 15.X. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 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-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
I think we know almost the entire story now. See LP: #1656391 The one piece still missing is what changed. Very clearly the armhf container tests passed for several months, and then stopped working. My best guess is that they switched from using privileged containers to unprivileged containers. In any event, I'm going to close this bug. See the above referenced bug for further discussion. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: lvm2 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Incomplete ** Changed in: lvm2 (Ubuntu) Status: Invalid => Incomplete ** Changed in: multipath-tools (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/1655735 Title: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Status in linux package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: Incomplete Status in multipath-tools package in Ubuntu: Incomplete Bug description: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu- image/20170111_171929_431b1@/log.gz Scroll to the bottom and you see this: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met /dev/mapper/control: mknod failed: Operation not permitted Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met Don't be misled by the gadget.yamls which name different architectures. ubuntu-image should be able to build a disk image for any architecture on any architecture. What this test does is build the image, then run kpartx to map the partitions in the image, and then mount the partitions. It doesn't do anything other than ensure that the partitions can be mounted, and this is where it's failing. This test succeeds on amd64, i386, and ppc64el. It's never passed on s390x so that's not a regression. It *used* to pass on armhf even on Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the regression. I will bugtask this to libdevmapper and kpartx since it's possibly a bug in one of those packages (though I still suspect the kernel). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-11-generic 4.9.0-11.12 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barry 5414 F pulseaudio /dev/snd/controlC0: barry 5414 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 11 13:10:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864 InstallationDate: Installed on 2016-01-22 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro RelatedPackageVersions: linux-restricted-modules-4.9.0-11-generic N/A linux-backports-modules-4.9.0-11-generic N/A linux-firmware1.162 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-UD5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-UD5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://l
[Kernel-packages] [Bug 1651520] Re: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state
Christopher, I've installed the latest mainline kernel (4.9.3-040903-generic #201701120631) and performed quick stress testing. At the moment everything works fine, but as me and nico mentioned, this bug is not always reproducable even on the kernels where it definitely exists. I will work on this latest kernel and notify in case of any related issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651520 Title: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state Status in linux package in Ubuntu: Incomplete Bug description: Text in Unity windows becomes a total mess after suspending and waking up Ubuntu 16.04. Text content in most of system and native windows are scrambled including terminal, nautilus, native apps EXCEPT Java apps (browsers and LibreOffice work fine). I had this issue multiple times, but it is not always reproducible. This bug occurs in linux-image-generic 4.4.0.53. It does not appear with linux-image-extra-4.4.0-51-generic 4.4.0-51.72 amd64. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lav2950 F pulseaudio /dev/snd/controlC0: lav2950 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-25 (801 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20A8S28400 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 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 Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-11 (114 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET39WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A8S28400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A8S28400 dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651520] Re: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state
nico (nicolas-pourcelot), it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651520 Title: Scrambled UI: Text in the Unity windows disappears/mixed after the resume from the screen idle state Status in linux package in Ubuntu: Incomplete Bug description: Text in Unity windows becomes a total mess after suspending and waking up Ubuntu 16.04. Text content in most of system and native windows are scrambled including terminal, nautilus, native apps EXCEPT Java apps (browsers and LibreOffice work fine). I had this issue multiple times, but it is not always reproducible. This bug occurs in linux-image-generic 4.4.0.53. It does not appear with linux-image-extra-4.4.0-51-generic 4.4.0-51.72 amd64. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lav2950 F pulseaudio /dev/snd/controlC0: lav2950 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-25 (801 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20A8S28400 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=daa4b3a5-47b3-4c16-a1de-2dde0c540c4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 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 Tags: xenial Uname: Linux 4.4.0-57-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-11 (114 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET39WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A8S28400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET39WW(1.16):bd06/06/2014:svnLENOVO:pn20A8S28400:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S28400:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A8S28400 dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working
https://lists.ubuntu.com/archives/kernel-team/2017-January/081840.html ** Changed in: linux (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux (Ubuntu Zesty) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Changed in: linux (Ubuntu Zesty) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Zesty) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625318 Title: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: ---Problem Description--- If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing something like a ping flood. The PF interface will stop pinging. We found a small window were MMIO are bein g disabled during pci_enable_sriov is called. ---uname output--- 4.4.0-30-generic ---Additional Hardware Info--- It needs a Mellanox CX4 SRIOV capable to recreate this issue Machine Type = P8 ---Steps to Reproduce--- just configure the IP address of PF interface and start like a ping flood to that interface. then do this echo to enable SRIOV on the PF. echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs Then you will notice the ping flood will stop. A patch that will fix this issue was sent for review: https://patchwork.ozlabs.org/patch/671517/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625318] Re: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working
https://lists.ubuntu.com/archives/kernel-team/2017-January/081830.html ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** 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/1625318 Title: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: ---Problem Description--- If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing something like a ping flood. The PF interface will stop pinging. We found a small window were MMIO are bein g disabled during pci_enable_sriov is called. ---uname output--- 4.4.0-30-generic ---Additional Hardware Info--- It needs a Mellanox CX4 SRIOV capable to recreate this issue Machine Type = P8 ---Steps to Reproduce--- just configure the IP address of PF interface and start like a ping flood to that interface. then do this echo to enable SRIOV on the PF. echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs Then you will notice the ping flood will stop. A patch that will fix this issue was sent for review: https://patchwork.ozlabs.org/patch/671517/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Can you test v3.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ If it fails, we can "Reverse" bisect between v3.13 and v3.14-rc1. If v3.13 final boots fine, then that would indicate an Ubuntu specific SAUCE patch causing the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
This v4.10-rc3 kernel is now available. Can you give that version a test: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3 Also, was there a prior kernel version that did not exhibit this bug? If so, we can perform a kernel bisect to find the offending commit. ** Changed in: linux (Ubuntu) Importance: Medium => 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/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 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-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Guillaume, roots, Stéphane, can you also test with my PPA kernel from comment 30? It would help to know if your NVMe failures are also due to the patches we're reverting, or some other problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed 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 1655748] Re: linux-lts-vivid: 3.19.0-80.88~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => John Donnelly (jpdonnelly) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1655748 Title: linux-lts-vivid: 3.19.0-80.88~14.04.1 -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: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.19.0-80.88~14.04.1 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 -- derivative-trackers-created: true kernel-stable-master-bug: 1655745 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1655748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize
It appears these workaround patches introduced NVMe initialization problems on some non-Xen systems, see bug 1626894. I sent patches to revert this for xenial and yakkety. Instead, this problem should be fixed by a patch to Xen kernel code, in bug 1656831. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Zesty) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648449 Title: NVMe drives in Amazon AWS instance fail to initialize Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Invalid Bug description: [Impact] On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to initialize, and so aren't usable by the system. If one of the NVMe drives contains the root filesystem, the instance won't boot. [Test Case] Boot an AWS instance with a NVMe drive. It will fail to initialize the NVMe drive(s), and errors will appear in the system log (if the system boots at all). With a patched kernel, all NVMe drives are initialized and enumerated and work properly. [Regression Potential] Patching the NVMe driver may cause problems on other systems using NVMe drives. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1463120] Re: Failure to boot if fstab disk mounts fail
I work for a major educational system that utilizes Ubuntu Server (14.04, 16.04 LTS) instances on the Amazon Web Services cloud for critical infrastructure. This bug has come up a few times, where an admin has a typo or other error in /etc/fstab, pertaining to a non-OS filesystem (like an EFS data volume), and as a result, the system fails to boot. On a physical machine, this wouldn't be a big deal: press "S" to skip that mountpoint, and keep booting; or if that doesn't work, boot from live media and fix fstab. However, a cloud instance doesn't grant you those options: it hangs forever, and you have no physical keyboard, USB port, or optical drive with which to workaround the problem. I normally wouldn't suggest a certain priority on a bug, but this is a severe liability for anyone running Ubuntu in a cloud computing environment. Therefore, I must respectfully request that this bug be elevated to "Major" or "Critical" status. Thank-you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail Status in linux package in Ubuntu: Confirmed Bug description: I found this on my main 15.04 desktop but have reproduced it in a VM: 1. Install Ubuntu 15.04 (I included updates and non-free but I doubt that matters). 2. Add a bogus entry to /etc/fstab, eg: /dev/sdd1 /mnt/sdd1 ext4 errors=remount-ro 0 0 Note that /mnd/sdd1 exists but /dev/sdd1 does not 3. Reboot Expected: Failure to mount /dev/sdd1 reported and option to boot without mounting it Actual: System appears to hang, although it will eventually present a root terminal (with no indication of the cause of the problem). It appears to hang prior to switching graphical mode, with the result that any warnings/errors that are present on all boots but invisible because the screen clears before they're seen become visible for the first time incorrectly suggesting they are the cause of the problem. Removing (or commenting out) the problematic entries and rebooting allows the system to boot. HOWEVER: The grub boot menu now appears and any pre-existing menu timeout and default action seems to have been lost; it's now necessary to select a boot option on each boot. This may be a separate bug (or feature?). My actual case: I have external drives permanently connected via USB, however the USB card appears to have failed hence the drives are not accessible. With no clues (and being unfamiliar to systemd) working out why the system wouldn't boot was a tough job. --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1382 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=76b7b79b-0cdd-4605-bc58-381fad8fa67f InstallationDate: Installed on 2015-06-08 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=53f2fcea-e84c-4736-ac69-f34305a63432 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 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-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.143.1 RfKill: Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- Mailing list
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
linux-image-3.14.0-031400rc1-generic also boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Can you next test v3.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc1-trusty/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
LP: #1656391 And it's reproducible in an amd64 container run locally. So probably some change in the images or lxc. Maybe a new missing dependency? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655735 Title: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: New Status in multipath-tools package in Ubuntu: New Bug description: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu- image/20170111_171929_431b1@/log.gz Scroll to the bottom and you see this: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met /dev/mapper/control: mknod failed: Operation not permitted Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met Don't be misled by the gadget.yamls which name different architectures. ubuntu-image should be able to build a disk image for any architecture on any architecture. What this test does is build the image, then run kpartx to map the partitions in the image, and then mount the partitions. It doesn't do anything other than ensure that the partitions can be mounted, and this is where it's failing. This test succeeds on amd64, i386, and ppc64el. It's never passed on s390x so that's not a regression. It *used* to pass on armhf even on Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the regression. I will bugtask this to libdevmapper and kpartx since it's possibly a bug in one of those packages (though I still suspect the kernel). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-11-generic 4.9.0-11.12 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barry 5414 F pulseaudio /dev/snd/controlC0: barry 5414 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 11 13:10:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864 InstallationDate: Installed on 2016-01-22 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro RelatedPackageVersions: linux-restricted-modules-4.9.0-11-generic N/A linux-backports-modules-4.9.0-11-generic N/A linux-firmware1.162 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-UD5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-UD5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
linux-image-3.14.0-031400-generic also boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Ok scratch comment #13, must have been half asleep when I read comment
#12 , is there a status change I need to make for Trusty to move this
along? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1655683
Title:
kernel BUG at skbuff.h:1486 Insufficient linear data in skb
__skb_pull.part.7+0x4/0x6 [openvswitch]
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
In Progress
Bug description:
Since 2016-12-30 EST we have been experiencing repeated crashes of our
OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
line 1486:
1471 /**
1472 * skb_peek - peek at the head of an &sk_buff_head
1473 * @list_: list to peek at
1474 *
1475 * Peek an &sk_buff. Unlike most other operations you _MUST_
1476 * be careful with this one. A peek leaves the buffer on the
1477 * list and someone else may run off with it. You must hold
1478 * the appropriate locks or have a private queue to do this.
1479 *
1480 * Returns %NULL for an empty list or a pointer to the head element.
1481 * The reference count is not incremented and the reference is therefore
1482 * volatile. Use with caution.
1483 */
1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
1485 {
1486 struct sk_buff *skb = list_->next;
1487
1488 if (skb == (struct sk_buff *)list_)
1489 skb = NULL;
1490 return skb;
1491 }
This generally results in a full panic crash of the Neutron node and
connectivity breaking for VMs within the cloud. However, after using
crash-dumptools to collect information on the crashes over the past
three days, the kernel loaded by kexec during the crashdump appears in
about 2 out of 3 crash instances to continue running, and we see a
flap of the neutron services instead of a full panic that brings the
Neutron server down and necessitates a hard reboot.
I believe that this is a manifestation of the openvswitch and issue
described on 2017-01-08 as:
"OVS can only process L2 packets. But OVS GRE receive handler
can accept IP-GRE packets. When such packet is processed by
OVS datapath it can trigger following assert failure due
to insufficient linear data in skb."
https://patchwork.ozlabs.org/patch/712373/
I have not tested the patch provided above yet.
Other information and a few sample dmesg outputs from the crash:
(multiple dumps available)
# lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
# apt-cache policy openvswitch
N: Unable to locate package openvswitch
root@neutron01:/var/crash# apt-cache policy openvswitch-common
openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy openvswitch-switch
openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy neutron-plugin-openvswitch-agent
neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
*** 1:2014.1.5-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:2014.1.3-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1:2014.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
example dmesg:
## dmesg.201701060019
> [33100.131019] [ cut here ]
> [33100.131176] kernel BUG at
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
> [33100.131424] invalid opcode: [#1] SMP
> [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca
i2c_algo_bit ptp pps_c
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Thanks for testing! Can you next test 3.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635447] Re: Upgraded or Live USB 16.10 hangs at boot up blank purple screen
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Incomplete ** Changed in: linux (Ubuntu Yakkety) 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/1635447 Title: Upgraded or Live USB 16.10 hangs at boot up blank purple screen Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: My HP dm3z-2000 laptop works out of box for everything with Ubuntu 16.04, but fails to boot up after upgraded to 16.10. The upgrading went smooth itself. Laptop still can boot up with the latest 4.4 kernel of 16.04 which I did a regular update/upgrade before 16.10 release upgrade. Then I tried to boot with 16.10 Live USB and got same result. It also can boot up with kernel 4.8 if "acpi=off" parameter in place, but it takes long time to boot up. Everything seems fine after logged in and Unity 8 session works too. I couldn't get any log files since the system won't boot up, Ctrl+Alt+F1 does nothing. I can only see some messages in text boot mode, so I took a screen shot with my phone and attached here. Let me know how to get more details. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renm 2918 F pulseaudio /dev/snd/controlC1: renm 2918 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=7e8ca036-f81d-43e2-820a-1deadcffc2dc InstallationDate: Installed on 2016-10-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dm3t Notebook PC Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=19005996-db50-4249-9c73-17cf874dc678 ro acpi=off ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-22-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-15 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1482 dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd10/13/2010:svnHewlett-Packard:pnHPPaviliondm3tNotebookPC:pvr048620241F0011032:rvnHewlett-Packard:rn1482:rvr76.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm3t Notebook PC dmi.product.version: 048620241F0011032 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1643978] Re: hv_set_ifconfig creates corrupt file for multiple interfaces
Can you see if this is also happening with the latest Zesty kernel? All the packages are available from: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+build/11837051 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643978 Title: hv_set_ifconfig creates corrupt file for multiple interfaces Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: hv_set_ifconfig will create multiple GATEWAY entries in the interfaces file if there are multiple ethernet interfaces. This causes subsequent calls to ifup for the primary interface to fail with "RTNETLINK answers: File exists". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-cloud-tools-virtual-lts-xenial 4.4.0.47.50 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Nov 22 20:16 seq crw-rw+ 1 root audio 116, 33 Nov 22 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 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: Tue Nov 22 20:26:27 2016 HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916 InstallationDate: Installed on 2016-11-22 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic
Dear Sir, please , do not send me Bug reports : It is impossible for me to unsuscribe (bug) so I write to you. I thank you. On 13/01/2017 19:33, Joseph Salisbury wrote: > ** Changed in: linux (Ubuntu) > Status: Incomplete => 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/1655437 Title: 16.04 fails to boot with kernel 4.4.0-22-generic Status in linux package in Ubuntu: Fix Released Bug description: During ENIC driver development on our end, there was a mistake and the driver was built on the 4.4.0-22-generic kernel but we intended it to be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when testing the ENIC driver, it required a kernel upgrade and afterwards we found it wasn't able to boot due to some volume group issues it appears from the error messages. We fixed the driver issue on our end to target the correct inbox kernel version and it's working fine. We also haven't seen any issues with 16.04 and newer kernels. However, management is still concerned about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it possible to look into this issue? Or maybe would it be possible to get that kernel version removed from the package so a customer doesn't upgrade to that kernel after an offline install? I am able to replicate the issue easily by doing an offline install of 16.04 so the kernel does not get automatically upgraded, then upgrading to 4.4.0-22-generic and rebooting after install. 1. If I install 16.04 with auto partitioning, after updating the kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors. I’ve attached ubuntu.jpg for this. 2. If I install 16.04 with manual partitioning, I don’t see the vg not found, but OS still fails to boot and goes to shell. I’ve attached ubuntu2.jpg for this. Thanks, Jeff --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba InstallationDate: Installed on 2017-01-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp138s0 no wireless extensions. enp133s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSB-B420-M4 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: B420M4.3.1.2f.0.110720161154 dmi.board.name: UCSB-B420-M4 dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-16458-06 dmi.chassis.type: 18 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-4777-02 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02: dmi.product.name: UCSB-B420-M4 dmi.product.version: 03 dmi.sys.vendor: Cisco Systems Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize
** Changed in: linux (Ubuntu Zesty) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648449 Title: NVMe drives in Amazon AWS instance fail to initialize Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Won't Fix Bug description: [Impact] On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to initialize, and so aren't usable by the system. If one of the NVMe drives contains the root filesystem, the instance won't boot. [Test Case] Boot an AWS instance with a NVMe drive. It will fail to initialize the NVMe drive(s), and errors will appear in the system log (if the system boots at all). With a patched kernel, all NVMe drives are initialized and enumerated and work properly. [Regression Potential] Patching the NVMe driver may cause problems on other systems using NVMe drives. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1656372] [NEW] HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install.
Dear Sir, please , do not send me Bug reports : It is impossible for me to unsuscribe (bug) so I write to you. I thank you. On 13/01/2017 18:56, Mic Gotschall wrote: > Public bug reported: > > Installed Ubuntu on my laptop, and replaced the old Operating System > (Windows 10). The touchpad was working fine on Windows, and when I plug > in a mouse via USB it works as well. When I used the command "cat > /proc/bus/input/devices" a touchpad does not come up at all. I've been > trying to do some Google searches to find a fix but couldn't seem to > find one. Also did another install of Ubuntu to see if that was a > problem, but it still does not work. I am using Ubuntu release 16.04. > > 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.1 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC1: mic3233 F pulseaudio > /dev/snd/controlC0: mic3233 F pulseaudio > CurrentDesktop: Unity > Date: Thu Jan 12 19:46:34 2017 > HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 > InstallationDate: Installed on 2017-01-12 (0 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Hewlett-Packard HP 15 Notebook PC > ProcFB: 0 radeondrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed > root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/13/2013 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.07 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 2192 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 41.18 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr096E100014405F1620182:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion: > dmi.product.name: HP 15 Notebook PC > dmi.product.version: 096E100014405F1620182 > dmi.sys.vendor: Hewlett-Packard > > ** 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/1656372 Title: HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install. Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubuntu on my laptop, and replaced the old Operating System (Windows 10). The touchpad was working fine on Windows, and when I plug in a mouse via USB it works as well. When I used the command "cat /proc/bus/input/devices" a touchpad does not come up at all. I've been trying to do some Google searches to find a fix but couldn't seem to find one. Also did another install of Ubuntu to see if that was a problem, but it still does not work. I am using Ubuntu release 16.04. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mic3233 F pulseaudio /dev/snd/controlC0: mic3233 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:46:34 2017 HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2192 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dm
[Kernel-packages] [Bug 1649584] Re: Kernel update 3.13.0-105 causes SATA errors that end up remounting partitions as read-only
** Changed in: linux (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649584 Title: Kernel update 3.13.0-105 causes SATA errors that end up remounting partitions as read-only Status in linux package in Ubuntu: Incomplete Bug description: I started to notice SATA errors on my secondary hard disk (a Toshiba DT01ACA100 1TB, on an Intel DG45ID motherboard) after updating to 3.13.0-105. A simple file copy operation fails after a few megabytes and the drive stops responding. Sometimes it remounts itself as read- only, and sometimes it disappears from the drive list. On next reboot the drive is sort-of OK, but without the new files. I thought it was a hard disk failure, but reverting to 3.13.0-100 seems to fix the problem completely. SMART is OK and fsck checks passed. I'll try to post more details about my system later when I'm back to my home computer. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcuscf 2558 F pulseaudio /dev/snd/controlC0: marcuscf 2558 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=6b4b37f4-4276-4541-8e40-36a0b8570265 InstallationDate: Installed on 2012-05-12 (1676 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IwConfig: eth0 no wireless extensions. lono wireless extensions. NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=15c44951-2c8d-4c57-b8ff-e46deebb7b4a ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to trusty on 2016-11-03 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: IDG4510H.86A.0135.2011.0225.1100 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG45ID dmi.board.vendor: Intel Corporation dmi.board.version: AAE27729-310 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrIDG4510H.86A.0135.2011.0225.1100:bd02/25/2011:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-310:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656381] [NEW] Xen MSI setup code incorrectly re-uses cached pirq
Public bug reported: [Impact] This bug fixes the root problem reported in bug 1648449, so its description can be mostly reused here: On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to initialize, and so aren't usable by the system. If one of the NVMe drives contains the root filesystem, the instance won't boot. [Test Case] Boot an AWS instance with multiple NVMe drives. All except the first will fail to initialize, and errors will appear in the system log (if the system boots at all). With a patched kernel, all NVMe drives are initialized and enumerated and work properly. [Regression Potential] Patching the Xen MSI setup function may cause problems with other PCI devices using MSI/MSIX interrupts on a Xen guest. [Other Info] The patch from bug 1648449 was only a workaround, that changed the NVMe driver to not trigger this Xen bug. However, there have been reports of that patch causing non-Xen systems with NVMe drives to stop working, in bug 1626894. So, the best thing to do is revert the workaround patch (and its regression fix patch from bug 1651602) back to the original NVMe drive code, and apply the real Xen patch to fix the problem. That should restore functionality for non-Xen systems, and should allow Xen systems with multiple NVMe controllers to work. ** Affects: linux (Ubuntu) Importance: High Assignee: Dan Streetman (ddstreet) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (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/1656381 Title: Xen MSI setup code incorrectly re-uses cached pirq Status in linux package in Ubuntu: In Progress Bug description: [Impact] This bug fixes the root problem reported in bug 1648449, so its description can be mostly reused here: On an Amazon AWS instance that has NVMe drives, the NVMe drives fail to initialize, and so aren't usable by the system. If one of the NVMe drives contains the root filesystem, the instance won't boot. [Test Case] Boot an AWS instance with multiple NVMe drives. All except the first will fail to initialize, and errors will appear in the system log (if the system boots at all). With a patched kernel, all NVMe drives are initialized and enumerated and work properly. [Regression Potential] Patching the Xen MSI setup function may cause problems with other PCI devices using MSI/MSIX interrupts on a Xen guest. [Other Info] The patch from bug 1648449 was only a workaround, that changed the NVMe driver to not trigger this Xen bug. However, there have been reports of that patch causing non-Xen systems with NVMe drives to stop working, in bug 1626894. So, the best thing to do is revert the workaround patch (and its regression fix patch from bug 1651602) back to the original NVMe drive code, and apply the real Xen patch to fix the problem. That should restore functionality for non-Xen systems, and should allow Xen systems with multiple NVMe controllers to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1655437 Title: 16.04 fails to boot with kernel 4.4.0-22-generic Status in linux package in Ubuntu: Fix Released Bug description: During ENIC driver development on our end, there was a mistake and the driver was built on the 4.4.0-22-generic kernel but we intended it to be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when testing the ENIC driver, it required a kernel upgrade and afterwards we found it wasn't able to boot due to some volume group issues it appears from the error messages. We fixed the driver issue on our end to target the correct inbox kernel version and it's working fine. We also haven't seen any issues with 16.04 and newer kernels. However, management is still concerned about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it possible to look into this issue? Or maybe would it be possible to get that kernel version removed from the package so a customer doesn't upgrade to that kernel after an offline install? I am able to replicate the issue easily by doing an offline install of 16.04 so the kernel does not get automatically upgraded, then upgrading to 4.4.0-22-generic and rebooting after install. 1. If I install 16.04 with auto partitioning, after updating the kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors. I’ve attached ubuntu.jpg for this. 2. If I install 16.04 with manual partitioning, I don’t see the vg not found, but OS still fails to boot and goes to shell. I’ve attached ubuntu2.jpg for this. Thanks, Jeff --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba InstallationDate: Installed on 2017-01-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp138s0 no wireless extensions. enp133s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSB-B420-M4 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: B420M4.3.1.2f.0.110720161154 dmi.board.name: UCSB-B420-M4 dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-16458-06 dmi.chassis.type: 18 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-4777-02 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02: dmi.product.name: UCSB-B420-M4 dmi.product.version: 03 dmi.sys.vendor: Cisco Systems Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656372] Re: HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656372 Title: HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install. Status in linux package in Ubuntu: Incomplete Bug description: Installed Ubuntu on my laptop, and replaced the old Operating System (Windows 10). The touchpad was working fine on Windows, and when I plug in a mouse via USB it works as well. When I used the command "cat /proc/bus/input/devices" a touchpad does not come up at all. I've been trying to do some Google searches to find a fix but couldn't seem to find one. Also did another install of Ubuntu to see if that was a problem, but it still does not work. I am using Ubuntu release 16.04. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mic3233 F pulseaudio /dev/snd/controlC0: mic3233 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:46:34 2017 HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2192 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr096E100014405F1620182:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E100014405F1620182 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab
The bisect reported commit 50f208e18014589971583a8495987194724d56e4 as the first bad commit. I built a Xenial test kernel with this commit reverted. It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1650336/ Can you test this kernel and see if it resolves this bug? Note, you need to install both this linux-image and linux-image-extra .deb packages with this kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650336 Title: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel crash on boot when in /etc/fstab a nfsv4 entry is active When comment the line or set to noauto the kernel boot with no error and mounting the nfs shares (after uncomment ) is also possible without error 4.4.0-54 boots without this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656372] 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/1656372 Title: HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install. Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu on my laptop, and replaced the old Operating System (Windows 10). The touchpad was working fine on Windows, and when I plug in a mouse via USB it works as well. When I used the command "cat /proc/bus/input/devices" a touchpad does not come up at all. I've been trying to do some Google searches to find a fix but couldn't seem to find one. Also did another install of Ubuntu to see if that was a problem, but it still does not work. I am using Ubuntu release 16.04. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mic3233 F pulseaudio /dev/snd/controlC0: mic3233 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:46:34 2017 HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2192 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr096E100014405F1620182:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E100014405F1620182 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656372] [NEW] HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install.
Public bug reported: Installed Ubuntu on my laptop, and replaced the old Operating System (Windows 10). The touchpad was working fine on Windows, and when I plug in a mouse via USB it works as well. When I used the command "cat /proc/bus/input/devices" a touchpad does not come up at all. I've been trying to do some Google searches to find a fix but couldn't seem to find one. Also did another install of Ubuntu to see if that was a problem, but it still does not work. I am using Ubuntu release 16.04. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mic3233 F pulseaudio /dev/snd/controlC0: mic3233 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:46:34 2017 HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2192 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr096E100014405F1620182:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 096E100014405F1620182 dmi.sys.vendor: Hewlett-Packard ** 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/1656372 Title: HP touchpad does not detected touchpad in 'HP 15-d017cl' after fresh Ubuntu install. Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu on my laptop, and replaced the old Operating System (Windows 10). The touchpad was working fine on Windows, and when I plug in a mouse via USB it works as well. When I used the command "cat /proc/bus/input/devices" a touchpad does not come up at all. I've been trying to do some Google searches to find a fix but couldn't seem to find one. Also did another install of Ubuntu to see if that was a problem, but it still does not work. I am using Ubuntu release 16.04. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mic3233 F pulseaudio /dev/snd/controlC0: mic3233 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 12 19:46:34 2017 HibernationDevice: RESUME=UUID=14a44612-c96f-47d6-8f83-965f2101f368 InstallationDate: Installed on 2017-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=b1470648-b2c6-482e-893b-89e1dfe897fe 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.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2192 dmi.board.vendor: Hewlett-Packard dmi.board.version: 41.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP15NotebookPC:pvr096E100014405F1620182:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name:
[Kernel-packages] [Bug 1624164] Re: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo
@thornyon, why did you marked this bug as fix released? As far as I can see, linux-firmware still doesn't ship kbl_dmc_ver1.bin. I'd like to benefit from lower power usage that should come with this firmware. -- 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/1624164 Title: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Released Bug description: Also: Possible missing firmware /lib/firmware/i915/skl_guc_ver6.bin for module i915_bpo Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo Ubuntu 16.04 Xenial Packages: ii linux-firmware1.157.3 all Firmware for Linux kernel drivers ii linux-image-generic 4.4.0.36.38 amd64 Generic Linux kernel image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1624164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625318] Comment bridged from LTC Bugzilla
--- Comment From cls...@us.ibm.com 2017-01-13 11:51 EDT--- Thanks Gavin for working in this set of patches. Here are the upstream commits for this issue: >From f40ec3c748c6912f6266c56a7f7992de61b255ed Mon Sep 17 00:00:00 2001 From: Gavin Shan Date: Wed, 26 Oct 2016 12:15:35 +1100 Subject: PCI: Do any VF BAR updates before enabling the BARs >From 63880b230a4af502c56dde3d4588634c70c66006 Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 11:19:27 -0600 Subject: PCI: Ignore BAR updates on virtual functions >From 45d004f4afefdd8d79916ee6d97a9ecd94bb1ffe Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Tue, 29 Nov 2016 08:14:47 -0600 Subject: PCI: Update BARs using property bits appropriate for type >From 6ffa2489c51da77564a0881a73765ea2169f955d Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 09:15:52 -0600 Subject: PCI: Separate VF BAR updates from standard BAR updates >From 546ba9f8f22f71b0202b6ba8967be5cc6dae4e21 Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 16:43:06 -0600 Subject: PCI: Don't update VF BARs while VF memory space is enabled >From 286c2378aaccc7343ebf17ec6cd86567659caf70 Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 16:51:19 -0600 Subject: PCI: Remove pci_resource_bar() and pci_iov_resource_bar() >From 7a6d312b50e63f598f5b5914c4fd21878ac2b595 Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 17:21:02 -0600 Subject: PCI: Decouple IORESOURCE_ROM_ENABLE and PCI_ROM_ADDRESS_ENABLE >From 0b457dde3cf8b7c76a60f8e960f21bbd4abdc416 Mon Sep 17 00:00:00 2001 From: Bjorn Helgaas Date: Mon, 28 Nov 2016 16:17:41 -0600 Subject: PCI: Add comments about ROM BAR updating -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625318 Title: Ubuntu 16.10 KVM SRIOV: if enable sriov while ping flood is running ping will stop working Status in linux package in Ubuntu: Triaged Bug description: ---Problem Description--- If I enable SRIOV in a Mellanox CX4 card while a PF interface is doing something like a ping flood. The PF interface will stop pinging. We found a small window were MMIO are bein g disabled during pci_enable_sriov is called. ---uname output--- 4.4.0-30-generic ---Additional Hardware Info--- It needs a Mellanox CX4 SRIOV capable to recreate this issue Machine Type = P8 ---Steps to Reproduce--- just configure the IP address of PF interface and start like a ping flood to that interface. then do this echo to enable SRIOV on the PF. echo 8 > /sys/class/net/enP1p1s0f0/device/sriov_numvfs Then you will notice the ping flood will stop. A patch that will fix this issue was sent for review: https://patchwork.ozlabs.org/patch/671517/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
The linux-image-3.16.0-031600-generic kernel boots fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Abalan, you're subscribed to the "linux in Ubuntu" package, which is why you're receiving bug reports: https://bugs.launchpad.net/~fyma/+packagebugs -- You 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 linux source package in Xenial: Confirmed 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Abalan, you have also subscribed to the package "Linux in Ubuntu" as shown here: https://bugs.launchpad.net/~fyma/+packagebugs Because of this, you will receive bug notifications for EVERY bug filed against "Linux". YOu will need to unsubscribe from this package if you do not wish to receive these updates. OR, you will need to unsubscribe from each bug separately in the Bug Mail settings box that is towards the top of the page on the right hand side. Good Luck Jeff -- You 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 linux source package in Xenial: Confirmed 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 on
[Kernel-packages] [Bug 1655260] Re: Kernel freezes
Can you also test the latest upstream 4.4 kernel? This will tell us if the fix in 4.10-rc3 was already cc'd to stable. It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.42/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655260 Title: Kernel freezes Status in linux package in Ubuntu: Incomplete Bug description: Background info: - I'm using Ubuntu 16.04.1 LTS with kernel 4.4.0-57-generic, with i3wm and couple of terminals plus a web browser running on it. What happens: - On random time intervals the OS freezes and I don't have mouse, nor keyboard responding. The only thing I can do is cold restart. Searching through the syslog, I've got the following: Please see the attached file for more information. Best Regards, Viktor Penkov 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/pcmC1D0p: viktor 2809 F...m pulseaudio /dev/snd/controlC1: viktor 2809 F pulseaudio /dev/snd/controlC0: viktor 2809 F pulseaudio Date: Tue Jan 10 09:56:27 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d88c0a8e-3bfa-400e-a3fe-cb7d6cd262c9 InstallationDate: Installed on 2016-01-06 (369 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) MachineType: LENOVO 20BV003SBM ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic root=/dev/mapper/ubuntu--vg-root 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: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV003SBM 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:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BV003SBM:pvrThinkPadT450:rvnLENOVO:rn20BV003SBM:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BV003SBM dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656288] Re: Corruption of XER upon a Transaction Failure (Transactional Memory)
*** This bug is a duplicate of bug 1655041 ***
https://bugs.launchpad.net/bugs/1655041
** Tags removed: architecture-ppc64 targetmilestone-inin---
** Tags added: architecture-ppc64le targetmilestone-inin14042
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656288
Title:
Corruption of XER upon a Transaction Failure (Transactional Memory)
Status in linux package in Ubuntu:
New
Bug description:
Corruption of XER upon a Transaction Failure (Transactional Memory)
Upon a transaction failure the XER register is not being changed back
to the value that should be in the transaction's register checkpoint.
This is occurring when the transaction has been failed in hypervisor
mode.
This require the following commit-id: 0d808df06a44 ("KVM: PPC: Book3S
HV: Save/restore XER in checkpointed register state", 2016-11-07)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1598312] Re: Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz
Thank you for providing a patch, and making Ubuntu better. Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1598312 Title: Cannot scale AMD Turion CPU frequency. It runs on lowest 800MHz Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Bug description: http://askubuntu.com/questions/789096/cant-scale-frequencies-of-amd- turion-cpu-it-always-jumps-to-lowest The CPU does not scale frequency on kernel "4.2.0-41-generic #48~14.04.1-Ubuntu SMP Fri Jun 24 17:09:15". The notebook behaves very slow despite on Windows Vista it works great. Cpufreq-info program shows that there is a limit on the frequency setting between 800MHz and 800MHz. I tried to impose the frequency by setting the "performance policy" or by setting the limit in /etc/default/cpufrequency, but it does not work. Next I tried to check the BIOS limits, because there are some suggestions that some battery/power supply problems could cause the BIOS to set the limits on CPU freq but it is not there. The CPU freq scaling works good on 'linux-image-4.1.26-040126-generic' kernel. It does not work on this kernel "4.2.0-41-generic" and "linux- headers-4.2.0-38-generic". The current workaround is to switch off the ACPI by "acpi=off" boot parameter. Using this setting the CPU frequency scaling works but it makes the system single CPU core only. Hardware: HP Compaq 6715B notebook with AMD Turion CPU TL-58 and powernow-k8 cpufreq driver. I've heard some posts that on others HP notebooks there are similar problems with the freq scaling. $ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpuf...@vger.kernel.org, please. analyzing CPU 0: driver: powernow-k8 CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 109 us. hardware limits: 800 MHz - 1.90 GHz available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 800 MHz. cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 MHz:99,93% (1) analyzing CPU 1: driver: powernow-k8 CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 109 us. hardware limits: 800 MHz - 1.90 GHz available frequency steps: 1.90 GHz, 1.80 GHz, 1.60 GHz, 800 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 800 MHz and 800 MHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 800 MHz. cpufreq stats: 1.90 GHz:0,07%, 1.80 GHz:0,00%, 1.60 GHz:0,00%, 800 MHz:99,93% (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.2.0-41-generic 4.2.0-41.48~14.04.1 ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11 Uname: Linux 4.2.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 1 23:49:34 2016 InstallationDate: Installed on 2016-04-08 (83 days ago) InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: linux-lts-wily UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653843] Re: Bluetooth 04ca:3018 not working correctly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653843 Title: Bluetooth 04ca:3018 not working correctly Status in linux package in Ubuntu: In Progress Bug description: The bluetooth device is unable to discover any devices and when visible it cannot be discovered by any device. 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/pcmC0D0p: david 3259 F...m pulseaudio /dev/snd/controlC0: david 3259 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 4 03:07:28 2017 HibernationDevice: RESUME=UUID=53d59b56-5824-4ede-8752-62ef2e227c18 InstallationDate: Installed on 2016-12-22 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X556UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=5eed2705-b031-466b-8c03-d40f6ccfc133 ro quiet splash 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: 09/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UAK.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UAK.302:bd09/05/2016:svnASUSTeKCOMPUTERINC.:pnX556UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UAK 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/1653843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633634] Re: sr-iov not working on ubuntu 16.04 kvm
I replayed the bisect results and it looks like the following commit also needs to be tested: [92923ca3aacef63c92dc297a75ad0c6dfe4eab37] mm: meminit: only set page reserved in the memblock region Were you able to also test this 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/1633634 Title: sr-iov not working on ubuntu 16.04 kvm Status in linux package in Ubuntu: Confirmed Bug description: The exact same set up (hardware and commands I have made) worked perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The only thing I have changed between the 2 setups is adding to the network definition as the now default vfio also failed with qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 0x7fa68770) = -14 (Bad address) qemu: hardware error: vfio: DMA mapping failed, unable to continue If I am doing something wrong I apologise, this is my first bug report and I'm still relatively new to Linux. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-42-generic 4.4.0-42.62 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 14 20:11 seq crw-rw 1 root audio 116, 33 Oct 14 20:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 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: Fri Oct 14 23:05:26 2016 HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91 InstallationDate: Installed on 2016-10-08 (6 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU PRIMERGY TX1310 M1 PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on iommu=pt pci=assign-busses quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x dmi.board.name: D3219-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3219-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: TX1310M1 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1: dmi.product.name: PRIMERGY TX1310 M1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Hello Joseph, do you need me to test just kernel-image and headers? or
all debs in that dir, thanks for clarification.
-Andrew
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1655683
Title:
kernel BUG at skbuff.h:1486 Insufficient linear data in skb
__skb_pull.part.7+0x4/0x6 [openvswitch]
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
In Progress
Bug description:
Since 2016-12-30 EST we have been experiencing repeated crashes of our
OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
line 1486:
1471 /**
1472 * skb_peek - peek at the head of an &sk_buff_head
1473 * @list_: list to peek at
1474 *
1475 * Peek an &sk_buff. Unlike most other operations you _MUST_
1476 * be careful with this one. A peek leaves the buffer on the
1477 * list and someone else may run off with it. You must hold
1478 * the appropriate locks or have a private queue to do this.
1479 *
1480 * Returns %NULL for an empty list or a pointer to the head element.
1481 * The reference count is not incremented and the reference is therefore
1482 * volatile. Use with caution.
1483 */
1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
1485 {
1486 struct sk_buff *skb = list_->next;
1487
1488 if (skb == (struct sk_buff *)list_)
1489 skb = NULL;
1490 return skb;
1491 }
This generally results in a full panic crash of the Neutron node and
connectivity breaking for VMs within the cloud. However, after using
crash-dumptools to collect information on the crashes over the past
three days, the kernel loaded by kexec during the crashdump appears in
about 2 out of 3 crash instances to continue running, and we see a
flap of the neutron services instead of a full panic that brings the
Neutron server down and necessitates a hard reboot.
I believe that this is a manifestation of the openvswitch and issue
described on 2017-01-08 as:
"OVS can only process L2 packets. But OVS GRE receive handler
can accept IP-GRE packets. When such packet is processed by
OVS datapath it can trigger following assert failure due
to insufficient linear data in skb."
https://patchwork.ozlabs.org/patch/712373/
I have not tested the patch provided above yet.
Other information and a few sample dmesg outputs from the crash:
(multiple dumps available)
# lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
# apt-cache policy openvswitch
N: Unable to locate package openvswitch
root@neutron01:/var/crash# apt-cache policy openvswitch-common
openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy openvswitch-switch
openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy neutron-plugin-openvswitch-agent
neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
*** 1:2014.1.5-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:2014.1.3-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1:2014.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
example dmesg:
## dmesg.201701060019
> [33100.131019] [ cut here ]
> [33100.131176] kernel BUG at
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
> [33100.131424] invalid opcode: [#1] SMP
> [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca
i2c_algo_bit ptp pps_core megaraid_sas mdio
> [3
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Abalan, Please view the bug page and at the top on the Right Hand side, you should see a box that says the following, or something similar: You have subscriptions that may cause you to receive notifications, but you are not directly subscribed to this bug's notifications. Mute bug mailMute help Edit bug mail Please use that to mute the bug mail from this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 linux source package in Xenial: Confirmed 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
[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1654708 Title: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/ Status in zfs-linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 zfs-dkms 0.6.5.6-0ubuntu15 I cant mount/install my zpool. so i tried reinstalling zfslinux-utils, which gives me three error messages like this: "zfs-mount.service is a disabled" or a static unit, not starting it."... If something doesn't work I try googling error messages. most answers not totally like my problem but related to dkms, so I tried loading zfs-dkms and reinstalling zfslinux-utils. I created the zpool with id from /mnt/disk/by-id/ - which is zfs good- practice. This may be causing problems with the mount. I dont know... Cheers. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu15 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 DKMSKernelVersion: 4.4.0-58-generic Date: Sat Jan 7 15:58:15 2017 DuplicateSignature: dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12: error: too few arguments to function ‘posix_acl_valid’ InstallationDate: Installed on 2016-12-26 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225) PackageVersion: 0.6.5.6-0ubuntu15 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1654708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642096] Re: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1642096 Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: I did the usual apt-get upgrade and got this. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu14 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-47-generic (x86_64) Tue Nov 15 19:56:59 EST 2016 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.4.0-47-generic Date: Tue Nov 15 19:57:03 2016 InstallationDate: Installed on 2014-01-01 (1049 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageVersion: 0.6.5.6-0ubuntu14 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-09-05 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1642096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651199] Re: 16.04 - Kernel panic on docker server
Can you see if the latest 4.4 upstream kernel also fixes this bug? That will tell us if the fix in mainline was already cc'd to stable. It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.42/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651199 Title: 16.04 - Kernel panic on docker server Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80 [31016.061380] PGD 0 [31016.061380] Oops: 0010 [#1] SMP [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ixgbevf psmouse floppy [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic #74-Ubuntu [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016 [31016.061380] task: 880406496040 ti: 8804064e task.ti: 8804064e [31016.061380] RIP: 0010:[] [] __xen_evtchn_do_upcall+0x43/0x80 [31016.061380] RSP: 0018:88040fc43f78 EFLAGS: 00010082 [31016.061380] RAX: RBX: 88040fc4b840 RCX: 0001 [31016.061380] RDX: fffe RSI: 000123a0 RDI: 88040fc43f30 [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 0001 [31016.061380] R10: 0001 R11: R12: 0001 [31016.061380] R13: 0003 R14: R15: 8804064e [31016.178419] FS: () GS:88040fc4() knlGS: [31016.178419] CS: 0010 DS: ES: CR0: 80050033 [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 001406e0 [31016.178419] DR0: DR1: DR2: [31016.178419] DR3: DR6: fffe0ff0 DR7: 0400 [31016.178419] Stack: [31016.178419] 0003 88040fc43fa8 [31016.178419] 814d6bc0 81f36a00 8804064e3e90 81837f32 [31016.178419] 8804064e3de8 8804064e [31016.178419] Call Trace: [31016.178419] [31016.178419] [] xen_evtchn_do_upcall+0x30/0x40 [31016.178419] [] xen_hvm_callback_vector+0x82/0x90 [31016.178419] [31016.178419] [] ? native_safe_halt+0x6/0x10 [31016.178419] [] default_idle+0x1e/0xe0 [31016.239315] [] arch_cpu_idle+0xf/0x20 [31016.239899] [] default_idle_call+0x2a/0x40 [31016.239899] [] cpu_startup_entry+0x2f1/0x350 [31016.239899] [] start_secondary+0x154/0x190 [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 [31016.239899] RIP [] __xen_evtchn_do_upcall+0x43/0x80 [31016.239899] RSP [31016.239899] CR2: 82c4801e6bda [31016.239899] ---[ end trace 5b3e8ea32013e327 ]--- [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt [31016.239899] Kernel Offset: disabled We believe this appeared in the last 1-2mo of releases, since this started happening after we did a `apt-get upgrade` on our machines after a bit of a pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are Kubernetes minions, so I assume docker is likely the trigger. Unfortunately there aren't really any interesting logs in journalctl from the previous boot prior to the panic. Let me know what I can do to debug further. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 19 15:56 seq crw-rw 1 root audio 116, 33 Dec 19 15:56 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 o
[Kernel-packages] [Bug 1654414] Re: linux-image-4.8.0-32-generic causes complete system freeze
Can you also give the latest upstream 4.8 kernel a test? That will tell us if the fix in 4.10-rc2 was also cc'd to stable. It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1654414 Title: linux-image-4.8.0-32-generic causes complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: Complete system freeze when launching Eclipse. Started occurring since 4.8.0-27. Jan 5 22:52:20 ardesia kernel: [ 39.292905] BUG: unable to handle kernel NULL pointer dereference at (null) Jan 5 22:52:20 ardesia kernel: [ 39.292953] IP: [< (null)>] (null) Jan 5 22:52:20 ardesia kernel: [ 39.292979] PGD 0 Jan 5 22:52:20 ardesia kernel: [ 39.292996] Oops: 0010 [#1] SMP Jan 5 22:52:20 ardesia kernel: [ 39.293013] Modules linked in: ccm bnep ti_usb_3410_5052 usbserial btusb btrtl uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btbcm btintel videodev bluetooth media snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic arc4 acer_wmi sparse_keymap binfmt_misc intel_rapl x86_pkg_temp_thermal nls_iso8859_1 kvm iwlmvm irqbypass crct10dif_pclmul crc32_pclmul snd_soc_skl ghash_clmulni_intel snd_soc_skl_ipc mac80211 aesni_intel snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match aes_x86_64 snd_soc_core lrw glue_helper snd_compress ablk_helper ac97_bus cryptd snd_pcm_dmaengine intel_cstate iwlwifi intel_rapl_perf snd_hda_intel snd_hda_codec cfg80211 joydev rtsx_pci_ms input_leds serio_raw memstick mei_me snd_hda_core mei snd_hwdep thinkpad_acpi snd_pcm shpchp nvram intel_pch_thermal snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid tpm_crb coretemp parport _pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops rtsx_pci ptp drm nvme pps_core nvme_core wmi video fjes Jan 5 22:52:20 ardesia kernel: [ 39.293657] CPU: 2 PID: 986 Comm: Xorg Tainted: G U 4.8.0-32-generic #34-Ubuntu Jan 5 22:52:20 ardesia kernel: [ 39.293696] Hardware name: LENOVO 20FBCTO1WW/20FBCTO1WW, BIOS N1FET37W (1.11 ) 03/15/2016 Jan 5 22:52:20 ardesia kernel: [ 39.293733] task: 8a9d0c0e1d80 task.stack: 8a9d08558000 Jan 5 22:52:20 ardesia kernel: [ 39.293761] RIP: 0010:[<>] [< (null)>] (null) Jan 5 22:52:20 ardesia kernel: [ 39.293798] RSP: 0018:8a9d0855bad8 EFLAGS: 00010286 Jan 5 22:52:20 ardesia kernel: [ 39.293823] RAX: 8a9cbc3a7000 RBX: 8a9d05f73c90 RCX: 0439 Jan 5 22:52:20 ardesia kernel: [ 39.293856] RDX: 0439 RSI: 8a9d05f729a8 RDI: 8a9cbc3a7000 Jan 5 22:52:20 ardesia kernel: [ 39.293887] RBP: 8a9d0855bb70 R08: 8a9cbc3a6b00 R09: Jan 5 22:52:20 ardesia kernel: [ 39.293918] R10: 8a9d03228301 R11: R12: Jan 5 22:52:20 ardesia kernel: [ 39.293952] R13: 8a9d05f729a8 R14: 8a9cbc3a6b00 R15: Jan 5 22:52:20 ardesia kernel: [ 39.293986] FS: 7fd12eb56a40() GS:8a9d2148() knlGS: Jan 5 22:52:20 ardesia kernel: [ 39.294021] CS: 0010 DS: ES: CR0: 80050033 Jan 5 22:52:20 ardesia kernel: [ 39.294048] CR2: CR3: 000402d3f000 CR4: 003406e0 Jan 5 22:52:20 ardesia kernel: [ 39.294081] DR0: DR1: DR2: Jan 5 22:52:20 ardesia kernel: [ 39.294116] DR3: DR6: fffe0ff0 DR7: 0400 Jan 5 22:52:20 ardesia kernel: [ 39.294147] Stack: Jan 5 22:52:20 ardesia kernel: [ 39.294159] c0457167 8a9d08f94b40 8a9d03228060 8a9d05f7 Jan 5 22:52:20 ardesia kernel: [ 39.294198] 8a9d05f729a8 8a9d0855bbb0 8a9cc0820900 00010439 Jan 5 22:52:20 ardesia kernel: [ 39.294237] 8a9cbc3a6b00 8a9d05f7 8a9d05f73c90 8a9d0855bb78 Jan 5 22:52:20 ardesia kernel: [ 39.294277] Call Trace: Jan 5 22:52:20 ardesia kernel: [ 39.294327] [] ? i915_gem_object_sync+0x177/0x510 [i915] Jan 5 22:52:20 ardesia kernel: [ 39.294382] [] ? intel_lr_context_pin+0x132/0x210 [i915] Jan 5 22:52:20 ardesia kernel: [ 39.294438] [] intel_execlists_submission+0x1cf/0x410 [i915] Jan 5 22:52:20 ardesia kernel: [ 39.294491] [] i915_gem_do_execbuffer.isra.24+0xde0/0x11a0 [i915] Jan 5 22:52:20 ardesia kernel: [ 39.294528] [] ? idr_get_empty_slot+0x189/0x370 Jan 5 22:52:20 ardesia kernel: [ 39.294558] [] ? kmem_cache_alloc_trace+0xd7/0x190 Jan 5 22:52:20 ardesia kernel:
[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure
** Changed in: linux (Ubuntu Xenial) Assignee: Kamal Mostafa (kamalmostafa) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You 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: Confirmed Status in linux source package in Yakkety: Confirmed 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 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
@jsalisbury, Thank you for the suggestions. I don't have the xenial kernel handy as I have the habit of running apt-get autoremove after upgrades. However, I will try the latest upstream kernel over this weekend and report the results. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem started with errors, OOM and an eventual kernel panic. It can run fine for about 3-4 hours or so. I see the following errors on syslog (also attached w/ other logs and information I can gather). Jan 9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long (3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 Jan 8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long (3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5 Jan 8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long (4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4 Jan 8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long (3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500 Jan 9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long (3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500 Jan 9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long (4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500 Jan 9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long (6170 > 6165), lowering kernel.perf_e
[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Thanks for the update. That means we should start testing prior to 4.4. Can you test 3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418339] Re: kernel set the wrong max_sectors_kb for 4K disks(sd.c)
** Tags removed: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1418339 Title: kernel set the wrong max_sectors_kb for 4K disks(sd.c) Status in linux package in Ubuntu: Fix Released Bug description: [Impact] Problem Description === We get following error messages on the console and IO fails. [ 63.322503] sd 0:2:2:0: [sdc] [ 63.322603] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE [ 63.322661] sd 0:2:2:0: [sdc] [ 63.322697] Sense Key : Illegal Request [current] [ 63.322757] sd 0:2:2:0: [sdc] [ 63.322792] Add. Sense: Invalid field in cdb [ 63.322839] sd 0:2:2:0: [sdc] CDB: [ 63.322874] Write(10): 2a 00 03 02 17 a0 00 00 80 00 [ 63.323038] blk_update_request: critical target error, dev sdc, sector 403750144 [ 63.323117] sd 0:2:2:0: [sdc] [ 63.323152] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE [ 63.323210] sd 0:2:2:0: [sdc] [ 63.323245] Sense Key : Illegal Request [current] [ 63.323303] sd 0:2:2:0: [sdc] [ 63.323338] Add. Sense: Invalid field in cdb [ 63.323385] sd 0:2:2:0: [sdc] CDB: [ 63.323420] Write(10): 2a 00 03 02 17 20 00 00 80 00 [ 63.323580] blk_update_request: critical target error, dev sdc, sector 403749120 [ 138.410612] EXT4-fs warning (device dm-2): ext4_end_bio:317: I/O error -121 writing to inode 265776 (offset 0 size 393216 starting block 33920) [ 138.410727] Buffer I/O error on device dm-2, logical block 33920 [ 138.410785] Buffer I/O error on device dm-2, logical block 33921 [ 138.410842] Buffer I/O error on device dm-2, logical block 33922 [ 138.410900] Buffer I/O error on device dm-2, logical block 33923 [ 138.410957] Buffer I/O error on device dm-2, logical block 33924 ---uname output--- Ubuntu 15.04 Machine Type = P8(Alpine) [Test Case] Steps to Reproduce = read/write to a 4K array. [Fix] commit 3a9794d32984b67a6d8992226918618f0e51e5d5 upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Do we happen to know what commits(Other than 69973b8308) are in 4.9 and newer that are also needed in 4.8? Do you want me to build a Yakkety test kernel with commit 69973b8308? -- You 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: Confirmed Status in linux source package in Yakkety: Confirmed 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 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
** Tags removed: kernel-da-key needs-reverse-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic ``` There was a typo in instructions (/etc/preferences.d should have been /etc/apt/preferences.d). As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix). I suggest you move /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to /etc/apt/preferences.d/ and downgrade related packages: $ apt update $ apt install linux-headers-generic/xenial-updates linux-tools-generic/xenial-updates linux-image-generic/xenial-updates ``` *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Yeah, ddstreet's -59 kernel boots just fine and sees my NVMe drives. Let me know if I can help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Confirmed 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 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)
Joseph, please note the following from the original bug report: I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649326 Title: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series) Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: The EFI stub loader produces consistent boot errors when booting Trusty starting with version 3.13.0-101-generic. This bug can be reproduced in many ways (using efibootmgr, an EFI shell, rEFInd, etc.). One approach is: 1) Install an EFI shell on the computer and set it as the default boot option using efibootmgr. 2) Copy the kernel and initrd files from /boot to /boot/efi. 3) Rename the kernel file to use a .efi filename extension. 4) Reboot into the EFI shell. 5) Try to launch the kernel with a command like: fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 initrd=\initrd.img-3.13.0-104-generic The result will be a hung or crashed system. (In VirtualBox, in which I've tested this, the VM produces a "guru meditation" and the session terminates.) I myself have tested only with the 3.13.0-104 kernel; however, reports from others indicate that the problem began with the 3.13.0-101 kernel. See this Kubuntu forum thread for details: https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest- kernels Note that early on, this thread focuses on rEFInd; however, the bug can be reproduced with other boot managers, including the EFI shell, as described in the preceding procedure, so I do not believe this is a rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux kernel, and I believe it's this component that's failing. The problem does NOT occur when using GRUB to launch the kernel. (GRUB does not rely on the EFI stub loader.) I have NOT encountered the problem with Xenial and its 4.4.0-series kernels (last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from series beyond 3.13.0. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 1675 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc InstallationDate: Installed on 2014-04-27 (960 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.22 RfKill: Tags: trusty Uname: Linux 3.13.0-106-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Are you able to test various kernels? If so, it might be good to test the mainline kernel to see if the bug is already fixed in mainline. It is available from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc3 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 linux source package in Xenial: Confirmed 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:
