[Kernel-packages] [Bug 1575506] [NEW] Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038
Public bug reported: When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following kernel oops is triggered. [ 93.309158] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.309160] pgd = 8007a5914000 [ 93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, *pmd= [ 93.309167] Internal error: Oops: 9606 [#1] SMP [ 93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb [ 93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 4.4.0-15.31-generic #31+clk.1 [ 93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta Feb 2 2016 [ 93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 8007a7a3 [ 93.309217] PC is at fput+0x20/0xd0 [ 93.309222] LR is at vma_do_fput+0x24/0x48 [ 93.309223] pc : [] lr : [] pstate: 6145 [ 93.309224] sp : 8007a7a33e20 [ 93.309226] x29: 8007a7a33e20 x28: 8007a7a3 [ 93.309228] x27: 0003 x26: 8007a59886e8 [ 93.309229] x25: 800746248ed8 x24: 8011 [ 93.309231] x23: x22: 8091b780 [ 93.309232] x21: 1000 x20: [ 93.309233] x19: x18: 1140 [ 93.309235] x17: 8915f2c0 x16: 80133de0 [ 93.309236] x15: 893c2000 x14: [ 93.309237] x13: 0003e800 x12: 734b0200 [ 93.309239] x11: 003d0f00 x10: 0930 [ 93.309240] x9 : x8 : [ 93.309242] x7 : 80074645ac10 x6 : 00680f43 [ 93.309243] x5 : 00680f4f x4 : 0064 [ 93.309245] x3 : 00680f53 x2 : 0038 [ 93.309246] x1 : 8091b780 x0 : 801fe1f4 [ 93.309248] Process stress-ng-remap (pid: 2062, stack limit = 0x8007a7a30020) [ 93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000) [ 93.309252] 3e20: 8007a7a33e40 801fe1f4 8007a59886e8 [ 93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 80d8e000 [ 93.309255] 3e60: c85b2280 80085c70 88301000 [ 93.309257] 3e80: 89161ea8 8000 0015 [ 93.309258] 3ea0: 011d 00ea 80901000 8007a7a3 [ 93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 1000 [ 93.309261] 3ee0: 0200 [ 93.309262] 3f00: 00d1 00d1 00ea 2626 [ 93.309264] 3f20: 0101010101010101 001e 0018 0003e800 [ 93.309266] 3f40: 893c2cc0 004828c0 89161ea0 [ 93.309267] 3f60: 1140 0050 88301000 1000 [ 93.309269] 3f80: 1000 c85b2368 88d96fd0 4650 [ 93.309270] 3fa0: 004558f0 c85b34b8 0048f000 c85b2280 [ 93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 8000 [ 93.309273] 3fe0: 8830 00ea 8007a7a33fe8 [ 93.309274] Call trace: [ 93.309277] [] fput+0x20/0xd0 [ 93.309280] [] vma_do_fput+0x24/0x48 [ 93.309283] [] SyS_remap_file_pages+0x258/0x2a0 [ 93.309287] [] el0_svc_naked+0x24/0x28 [ 93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) [ 93.309308] ---[ end trace e42a31bddbea7038 ]--- [ 93.672808] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.672809] pgd = 8007d8f22000 [ 93.672813] [0038] *pgd=0047d9123003, *pud=0047d9124003, *pmd= [ 93.672817] Internal error: Oops: 9606 [#2] SMP [ 93.672853] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce
[Kernel-packages] [Bug 1551747] Re: ubuntu-fan causes issues during network configuration
** Changed in: snappy Status: New => Confirmed ** Changed in: snappy Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1551747 Title: ubuntu-fan causes issues during network configuration Status in Snappy: Confirmed Status in ubuntu-fan package in Ubuntu: Confirmed Bug description: it seems that ubuntu-fan is causing issues with network configuration. On 16.04 daily image: root@localhost:~# snappy list NameDate Version Developer canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-02-22 16.04.0-10.armhf canonical I see this when I'm activating a wifi card on a raspberry pi 2. root@localhost:~# ifdown wlan0 ifdown: interface wlan0 not configured root@localhost:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/c4:e9:84:17:31:9b Sending on LPF/wlan0/c4:e9:84:17:31:9b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e) DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e) DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081) DHCPOFFER of 192.168.0.170 from 192.168.0.251 DHCPACK of 192.168.0.170 from 192.168.0.251 RTNETLINK answers: File exists bound to 192.168.0.170 -- renewal in 17145 seconds. run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 Failed to bring up wlan0. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1551747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575506] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1575506 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575506 Title: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 0038 Status in linux package in Ubuntu: Incomplete Bug description: When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following kernel oops is triggered. [ 93.309158] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.309160] pgd = 8007a5914000 [ 93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, *pmd= [ 93.309167] Internal error: Oops: 9606 [#1] SMP [ 93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb [ 93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 4.4.0-15.31-generic #31+clk.1 [ 93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta Feb 2 2016 [ 93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 8007a7a3 [ 93.309217] PC is at fput+0x20/0xd0 [ 93.309222] LR is at vma_do_fput+0x24/0x48 [ 93.309223] pc : [] lr : [] pstate: 6145 [ 93.309224] sp : 8007a7a33e20 [ 93.309226] x29: 8007a7a33e20 x28: 8007a7a3 [ 93.309228] x27: 0003 x26: 8007a59886e8 [ 93.309229] x25: 800746248ed8 x24: 8011 [ 93.309231] x23: x22: 8091b780 [ 93.309232] x21: 1000 x20: [ 93.309233] x19: x18: 1140 [ 93.309235] x17: 8915f2c0 x16: 80133de0 [ 93.309236] x15: 893c2000 x14: [ 93.309237] x13: 0003e800 x12: 734b0200 [ 93.309239] x11: 003d0f00 x10: 0930 [ 93.309240] x9 : x8 : [ 93.309242] x7 : 80074645ac10 x6 : 00680f43 [ 93.309243] x5 : 00680f4f x4 : 0064 [ 93.309245] x3 : 00680f53 x2 : 0038 [ 93.309246] x1 : 8091b780 x0 : 801fe1f4 [ 93.309248] Process stress-ng-remap (pid: 2062, stack limit = 0x8007a7a30020) [ 93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000) [ 93.309252] 3e20: 8007a7a33e40 801fe1f4 8007a59886e8 [ 93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 80d8e000 [ 93.309255] 3e60: c85b2280 80085c70 88301000 [ 93.309257] 3e80: 89161ea8 8000 0015 [ 93.309258] 3ea0: 011d 00ea 80901000 8007a7a3 [ 93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 1000 [ 93.309261] 3ee0: 0200 [ 93.309262] 3f00: 00d1 00d1 00ea 2626 [ 93.309264] 3f20: 0101010101010101 001e 0018 0003e800 [ 93.309266] 3f40: 893c2cc0 004828c0 89161ea0 [ 93.309267] 3f60: 1140 0050 88301000 1000 [ 93.309269] 3f80: 1000 c85b2368 88d96fd0 4650 [ 93.309270] 3fa0: 004558f0 c85b34b8 0048f000 c85b2280 [ 93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 8000 [ 93.309273] 3fe0: 8830 00ea 8007a7a33fe8 [ 93.309274] Call trace: [ 93.309277] [] fput+0x20/0xd0 [ 93.309280] [] vma_do_fput+0x24/0x48
[Kernel-packages] [Bug 1575451] Re: PIE mode breaks building kernel modules
*** This bug is a duplicate of bug 1574982 *** https://bugs.launchpad.net/bugs/1574982 ** This bug has been marked a duplicate of bug 1574982 Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575451 Title: PIE mode breaks building kernel modules Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-352 package in Ubuntu: New Status in nvidia-graphics-drivers-361 package in Ubuntu: New Bug description: DKMS make.log for nvidia-364-364.19 for kernel 4.4.0-22-generic (x86_64) Tue Apr 26 21:55:12 EDT 2016 make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-364/364.19/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler SYMLINK /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-kernel.o SYMLINK /var/lib/dkms/nvidia-364/364.19/build/nvidia-modeset/nv-modeset-kernel.o CONFTEST: INIT_WORK CONFTEST: remap_pfn_range CONFTEST: follow_pfn CONFTEST: vmap CONFTEST: set_pages_uc CONFTEST: set_memory_uc CONFTEST: change_page_attr CONFTEST: set_memory_array_uc CONFTEST: pci_get_class CONFTEST: pci_choose_state CONFTEST: vm_insert_page CONFTEST: acpi_device_id CONFTEST: acquire_console_sem CONFTEST: console_lock CONFTEST: kmem_cache_create CONFTEST: on_each_cpu CONFTEST: smp_call_function CONFTEST: acpi_evaluate_integer CONFTEST: ioremap_cache CONFTEST: ioremap_wc CONFTEST: acpi_walk_namespace CONFTEST: pci_domain_nr CONFTEST: pci_dma_mapping_error CONFTEST: sg_alloc_table CONFTEST: sg_init_table CONFTEST: pci_get_domain_bus_and_slot CONFTEST: get_num_physpages CONFTEST: efi_enabled CONFTEST: proc_create_data CONFTEST: pde_data CONFTEST: proc_remove CONFTEST: pm_vt_switch_required CONFTEST: drm_driver_has_set_busid CONFTEST: xen_ioemu_inject_msi CONFTEST: phys_to_dma CONFTEST: write_cr4 CONFTEST: of_parse_phandle CONFTEST: get_dma_ops CONFTEST: for_each_online_node CONFTEST: node_end_pfn CONFTEST: pci_bus_address CONFTEST: remap_page_range CONFTEST: address_space_init_once CONFTEST: kbasename CONFTEST: fatal_signal_pending CONFTEST: list_cut_position CONFTEST: hlist_for_each_entry CONFTEST: vzalloc CONFTEST: wait_on_bit_lock_argument_count CONFTEST: bitmap_clear CONFTEST: drm_dev_unref CONFTEST: drm_reinit_primary_mode_group CONFTEST: drm_atomic_set_mode_for_crtc CONFTEST: drm_atomic_clean_old_fb CONFTEST: i2c_adapter CONFTEST: pm_message_t CONFTEST: irq_handler_t CONFTEST: acpi_device_ops CONFTEST: acpi_op_remove CONFTEST: outer_flush_all CONFTEST: proc_dir_entry CONFTEST: scatterlist CONFTEST: sg_table CONFTEST: file_operations CONFTEST: vm_operations_struct CONFTEST: atomic_long_type CONFTEST: pci_save_state CONFTEST: file_inode CONFTEST: task_struct CONFTEST: kuid_t CONFTEST: dma_ops CONFTEST: dma_map_ops CONFTEST: noncoherent_swiotlb_dma_ops CONFTEST: fault_flags CONFTEST: atomic64_type CONFTEST: address_space CONFTEST: backing_dev_info CONFTEST: kernel_write CONFTEST: strnstr CONFTEST: iterate_dir CONFTEST: kstrtoull CONFTEST: get_user_pages_remote CONFTEST: drm_bus_present CONFTEST: drm_bus_has_bus_type CONFTEST: drm_bus_has_get_irq CONFTEST: drm_bus_has_get_name CONFTEST: drm_driver_has_legacy_dev_list CONFTEST: drm_crtc_state_has_connectors_changed CONFTEST: drm_init_functions_have_name_arg CONFTEST: drm_mode_connector_list_update_has_merge_type_bits_arg CONFTEST: dom0_kernel_present CONFTEST: drm_available CONFTEST: nvidia_grid_build CONFTEST: drm_atomic_available CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-frontend.o CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-instance.o CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv.o /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode /* _NVRM_COPYRIGHT_BEGIN_ ^ CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-acpi.o /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-instance.c:1:0: error: code model kernel does not support PIC mode /* _NVRM_COPYRIGHT_BEGIN_ ^ CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-chrdev.o script
[Kernel-packages] [Bug 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430
I have now finished bisecting the mainline kernel, and this is the commit that causes this problem: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=64d513ac31bd02a3c9b69ef0f36c196f9a9d commit 64d513ac31bd02a3c9b69ef0f36c196f9a9d Author: Christoph Hellwig Date: Thu Oct 8 09:28:04 2015 +0100 scsi: use host wide tags by default This patch changes the !blk-mq path to the same defaults as the blk-mq I/O path by always enabling block tagging, and always using host wide tags. We've had blk-mq available for a few releases so bugs with this mode should have been ironed out, and this ensures we get better coverage of over tagging setup over different configs. Signed-off-by: Christoph Hellwig Acked-by: Jens Axboe Reviewed-by: Hannes Reinecke Signed-off-by: James Bottomley -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561830 Title: Hard disk writes fail in 16.04 daily on nForce 430 Status in linux package in Ubuntu: Confirmed Bug description: I have an old PC I use for testing new operating systems. It has previously had Ubuntu 15.10 installed and working. The motherboard is an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce 6150 GPU. I have installed an Nvidia GT220 card to use for more modern video support. When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop- amd64.iso file downloaded 24/03/2016 18:17), it starts to write to the hard disk (Samsung HD103UJ), and after a short time the install got lots of disk write errors in kern.log. After the errors, the disk was unable to be read either, with "fdisk -l /dev/sda" failing to read a sector, where it had worked before starting the install. Unplugging the SATA cable to the drive and plugging it in again made the drive work again (on /dev/sdc), but another attempt to install failed with the same write errors. I noticed that the log had swap write errors also, so I rebooted the install DVD again, and this time did a "swapoff -a" command before attempting to install, but got the same errors again. So I found my Ubuntu 15.10 install DVD and tried a new install from that, which worked just fine. On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that the DVD based system would run normally, then tried mounting the EXT4 system partition I had just installed using the 15.10 install DVD. That worked, so I tried dd commands to do test writes to that partition. The following commands worked: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k but when I did this command: dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k after a while errors started appearing in kern.log, just as with the attempts to install 16.04. It appears that with sustained write activity, the errors will start and then the drive will become unusable until it is unplugged and plugged in again. I have attached the kern.log and syslog files from the 15.10 install that worked, and the 16.04 install attempt that failed. The first error message appears to be this: ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0 dhfis 0x1 dmafis 0x0 sdbfis 0x0 which leads me to suspect a problem with the handling of the SATA controller's interrupts. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2233 F pulseaudio /dev/snd/controlC1: ubuntu 2233 F pulseaudio CasperVersion: 1.368 DistroRelease: Ubuntu 16.04 IwConfig: enp0s20 no wireless extensions. lono wireless extensions. enp2s9no wireless extensions. LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- ProcVersionSignature: Ubuntu 4.4.0-15.31-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-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 RfKill: Tags: xen
[Kernel-packages] [Bug 1574690] fozzie (i386) - tests ran: 13, failed: 0
tests ran: 13, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.38/fozzie__4.4.0-22.38__2016-04-27_06-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574690 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-22.38 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1574690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1547838] Re: ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops
I guess this thread will be used to get the patch into mainline... http://marc.info/?l=linux-netdev&m=146174255118232&w=2 http://marc.info/?l=linux-netdev&m=146174254318229&w=2 http://marc.info/?l=linux-netdev&m=146174254318228&w=2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1547838 Title: ADMtek ADM8511 "Pegasus II" USB Ethernet causes oops Status in linux package in Ubuntu: Triaged Bug description: This is a rather old USB ethernet adapter. It worked fine for me with older distributions (including Ubuntu 10.04). I noticed it causing problems after upgrading to 14.04 and stopped using it as a result (since I needed reliable USB ethernet for work). I was also not completely sure if it was this device causing the issue or interplay between this device and a number of other networking USB devices that were used at work. I'd like to use this ethernet adapter at home but the machine is running Ubuntu 14.04 and the issue persists. I have collected some information that might help. I'm happy to try more things to collect information if that will help. I'm running Ubuntu 14.04 server 64-bit. I just rebooted so I'm running the latest updates. I was told to run ubuntu-bug linux but I'm not sure how much useful stuff is included in that. I'm including the kernel log which has some bad stuff happening in it. Not sure if it got the system-freezing oops or just the errors leading up to that. It feels like a bug in the driver that corrupts memory because I see issues with network-related things (eg. a ping crashed, but the next ping didn't), leading to a full-system freeze. This machine has been happily running Ubuntu for a looong time (though it was only recently upgraded to Ubuntu 14.04, previously it had been running 10.04). I have not had stability issues with the machine but plugging in the USB Ethernet reliably makes it freeze within minutes. The symptoms also match what I saw on my machine at work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sat Feb 20 21:23:29 2016 InstallationDate: Installed on 2015-12-31 (50 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.19.0-49-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0cffa533-89ec-44d8-b5f9-6efe69c1b955 InstallationDate: Installed on 2015-12-31 (67 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP EliteBook 8530w Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-49-generic root=UUID=d4c67c71-679c-4b9d-8e20-848149e8aedf ro debug ignore_loglevel crashkernel=384M-:128M ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 RelatedPackageVersions: linux-restricted-modules-3.19.0-49-generic N/A linux-backports-modules-3.19.0-49-generic N/A linux-firmware 1.127.20 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/08/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDV Ver. F.12 dmi.board.name: 30E7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.27 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.12:bd06/08/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.12:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8530w dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go
[Kernel-packages] [Bug 1531768] Re: [arm64] locks up some time after booting
This is a syslog from one boot up to the point where I hard-rebooted the instance because it was completely hanging. The kernel errors still look by and large like the ones from the original report (in JournalErrors.txt). ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531768/+attachment/4648738/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] locks up some time after booting Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038
The issue can be reproduced on '4.4.0-22-generic #38' too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575506 Title: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 0038 Status in linux package in Ubuntu: Incomplete Bug description: When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following kernel oops is triggered. [ 93.309158] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.309160] pgd = 8007a5914000 [ 93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, *pmd= [ 93.309167] Internal error: Oops: 9606 [#1] SMP [ 93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb [ 93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 4.4.0-15.31-generic #31+clk.1 [ 93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta Feb 2 2016 [ 93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 8007a7a3 [ 93.309217] PC is at fput+0x20/0xd0 [ 93.309222] LR is at vma_do_fput+0x24/0x48 [ 93.309223] pc : [] lr : [] pstate: 6145 [ 93.309224] sp : 8007a7a33e20 [ 93.309226] x29: 8007a7a33e20 x28: 8007a7a3 [ 93.309228] x27: 0003 x26: 8007a59886e8 [ 93.309229] x25: 800746248ed8 x24: 8011 [ 93.309231] x23: x22: 8091b780 [ 93.309232] x21: 1000 x20: [ 93.309233] x19: x18: 1140 [ 93.309235] x17: 8915f2c0 x16: 80133de0 [ 93.309236] x15: 893c2000 x14: [ 93.309237] x13: 0003e800 x12: 734b0200 [ 93.309239] x11: 003d0f00 x10: 0930 [ 93.309240] x9 : x8 : [ 93.309242] x7 : 80074645ac10 x6 : 00680f43 [ 93.309243] x5 : 00680f4f x4 : 0064 [ 93.309245] x3 : 00680f53 x2 : 0038 [ 93.309246] x1 : 8091b780 x0 : 801fe1f4 [ 93.309248] Process stress-ng-remap (pid: 2062, stack limit = 0x8007a7a30020) [ 93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000) [ 93.309252] 3e20: 8007a7a33e40 801fe1f4 8007a59886e8 [ 93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 80d8e000 [ 93.309255] 3e60: c85b2280 80085c70 88301000 [ 93.309257] 3e80: 89161ea8 8000 0015 [ 93.309258] 3ea0: 011d 00ea 80901000 8007a7a3 [ 93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 1000 [ 93.309261] 3ee0: 0200 [ 93.309262] 3f00: 00d1 00d1 00ea 2626 [ 93.309264] 3f20: 0101010101010101 001e 0018 0003e800 [ 93.309266] 3f40: 893c2cc0 004828c0 89161ea0 [ 93.309267] 3f60: 1140 0050 88301000 1000 [ 93.309269] 3f80: 1000 c85b2368 88d96fd0 4650 [ 93.309270] 3fa0: 004558f0 c85b34b8 0048f000 c85b2280 [ 93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 8000 [ 93.309273] 3fe0: 8830 00ea 8007a7a33fe8 [ 93.309274] Call trace: [ 93.309277] [] fput+0x20/0xd0 [ 93.309280] [] vma_do_fput+0x24/0x48 [ 93.309283] [] SyS_remap_file_pages+0x258/0x2a0 [ 93.309287] [] el0_svc_naked+0x24/0x28 [ 93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) [ 93.309308] ---[ end trace e42a31bddbea7038 ]--- [ 93.672808] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.672809] pgd = 8007d8f22000 [ 93.672813] [0038] *pgd=0047d9123003, *pud=0047d9124003, *pmd=
[Kernel-packages] [Bug 1575467] [NEW] Ubuntu 16.04 consistently freezes up / hangs
You have been subscribed to a public bug: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13 bus info: pci@:00:13.0 version: 0e width: 32 bits clock: 66MHz capabilities: storage msi pm ahci_1.0 bus_master cap_list configuration: driver=ahci latency=0 resources: irq:88 ioport:f070(size=8) ioport:f060(size=4) ioport:f050(size=8) ioport:f040(size=4) ioport:f020(size=32) memory:d071c000-d071c7ff *-usb description: USB controller product: Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI
[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs
seems locks are more likely to be a kernel/driver issue than a desktop ui one ** Package changed: unity (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: New Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13 bu
[Kernel-packages] [Bug 1574690] fozzie (amd64) - tests ran: 23, failed: 1
tests ran: 23, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-22.38/fozzie__4.4.0-22.38__2016-04-27_07-57-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/1574690 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-22.38 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1574690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038
** 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/1575506 Title: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 0038 Status in linux package in Ubuntu: Confirmed Bug description: When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following kernel oops is triggered. [ 93.309158] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.309160] pgd = 8007a5914000 [ 93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, *pmd= [ 93.309167] Internal error: Oops: 9606 [#1] SMP [ 93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb [ 93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 4.4.0-15.31-generic #31+clk.1 [ 93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta Feb 2 2016 [ 93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 8007a7a3 [ 93.309217] PC is at fput+0x20/0xd0 [ 93.309222] LR is at vma_do_fput+0x24/0x48 [ 93.309223] pc : [] lr : [] pstate: 6145 [ 93.309224] sp : 8007a7a33e20 [ 93.309226] x29: 8007a7a33e20 x28: 8007a7a3 [ 93.309228] x27: 0003 x26: 8007a59886e8 [ 93.309229] x25: 800746248ed8 x24: 8011 [ 93.309231] x23: x22: 8091b780 [ 93.309232] x21: 1000 x20: [ 93.309233] x19: x18: 1140 [ 93.309235] x17: 8915f2c0 x16: 80133de0 [ 93.309236] x15: 893c2000 x14: [ 93.309237] x13: 0003e800 x12: 734b0200 [ 93.309239] x11: 003d0f00 x10: 0930 [ 93.309240] x9 : x8 : [ 93.309242] x7 : 80074645ac10 x6 : 00680f43 [ 93.309243] x5 : 00680f4f x4 : 0064 [ 93.309245] x3 : 00680f53 x2 : 0038 [ 93.309246] x1 : 8091b780 x0 : 801fe1f4 [ 93.309248] Process stress-ng-remap (pid: 2062, stack limit = 0x8007a7a30020) [ 93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000) [ 93.309252] 3e20: 8007a7a33e40 801fe1f4 8007a59886e8 [ 93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 80d8e000 [ 93.309255] 3e60: c85b2280 80085c70 88301000 [ 93.309257] 3e80: 89161ea8 8000 0015 [ 93.309258] 3ea0: 011d 00ea 80901000 8007a7a3 [ 93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 1000 [ 93.309261] 3ee0: 0200 [ 93.309262] 3f00: 00d1 00d1 00ea 2626 [ 93.309264] 3f20: 0101010101010101 001e 0018 0003e800 [ 93.309266] 3f40: 893c2cc0 004828c0 89161ea0 [ 93.309267] 3f60: 1140 0050 88301000 1000 [ 93.309269] 3f80: 1000 c85b2368 88d96fd0 4650 [ 93.309270] 3fa0: 004558f0 c85b34b8 0048f000 c85b2280 [ 93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 8000 [ 93.309273] 3fe0: 8830 00ea 8007a7a33fe8 [ 93.309274] Call trace: [ 93.309277] [] fput+0x20/0xd0 [ 93.309280] [] vma_do_fput+0x24/0x48 [ 93.309283] [] SyS_remap_file_pages+0x258/0x2a0 [ 93.309287] [] el0_svc_naked+0x24/0x28 [ 93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) [ 93.309308] ---[ end trace e42a31bddbea7038 ]--- [ 93.672808] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.672809] pgd = 8007d8f22000 [ 93.672813] [0038] *pgd=0047d9123003, *pud=0047d9124003, *pmd=
[Kernel-packages] [Bug 1575467] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1575467 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Incomplete Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_contr
[Kernel-packages] [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038
Upstream 4.6-rc6 hasn't this 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/1575506 Title: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 0038 Status in linux package in Ubuntu: Confirmed Bug description: When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following kernel oops is triggered. [ 93.309158] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.309160] pgd = 8007a5914000 [ 93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, *pmd= [ 93.309167] Internal error: Oops: 9606 [#1] SMP [ 93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb [ 93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 4.4.0-15.31-generic #31+clk.1 [ 93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta Feb 2 2016 [ 93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 8007a7a3 [ 93.309217] PC is at fput+0x20/0xd0 [ 93.309222] LR is at vma_do_fput+0x24/0x48 [ 93.309223] pc : [] lr : [] pstate: 6145 [ 93.309224] sp : 8007a7a33e20 [ 93.309226] x29: 8007a7a33e20 x28: 8007a7a3 [ 93.309228] x27: 0003 x26: 8007a59886e8 [ 93.309229] x25: 800746248ed8 x24: 8011 [ 93.309231] x23: x22: 8091b780 [ 93.309232] x21: 1000 x20: [ 93.309233] x19: x18: 1140 [ 93.309235] x17: 8915f2c0 x16: 80133de0 [ 93.309236] x15: 893c2000 x14: [ 93.309237] x13: 0003e800 x12: 734b0200 [ 93.309239] x11: 003d0f00 x10: 0930 [ 93.309240] x9 : x8 : [ 93.309242] x7 : 80074645ac10 x6 : 00680f43 [ 93.309243] x5 : 00680f4f x4 : 0064 [ 93.309245] x3 : 00680f53 x2 : 0038 [ 93.309246] x1 : 8091b780 x0 : 801fe1f4 [ 93.309248] Process stress-ng-remap (pid: 2062, stack limit = 0x8007a7a30020) [ 93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000) [ 93.309252] 3e20: 8007a7a33e40 801fe1f4 8007a59886e8 [ 93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 80d8e000 [ 93.309255] 3e60: c85b2280 80085c70 88301000 [ 93.309257] 3e80: 89161ea8 8000 0015 [ 93.309258] 3ea0: 011d 00ea 80901000 8007a7a3 [ 93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 1000 [ 93.309261] 3ee0: 0200 [ 93.309262] 3f00: 00d1 00d1 00ea 2626 [ 93.309264] 3f20: 0101010101010101 001e 0018 0003e800 [ 93.309266] 3f40: 893c2cc0 004828c0 89161ea0 [ 93.309267] 3f60: 1140 0050 88301000 1000 [ 93.309269] 3f80: 1000 c85b2368 88d96fd0 4650 [ 93.309270] 3fa0: 004558f0 c85b34b8 0048f000 c85b2280 [ 93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 8000 [ 93.309273] 3fe0: 8830 00ea 8007a7a33fe8 [ 93.309274] Call trace: [ 93.309277] [] fput+0x20/0xd0 [ 93.309280] [] vma_do_fput+0x24/0x48 [ 93.309283] [] SyS_remap_file_pages+0x258/0x2a0 [ 93.309287] [] el0_svc_naked+0x24/0x28 [ 93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) [ 93.309308] ---[ end trace e42a31bddbea7038 ]--- [ 93.672808] Unable to handle kernel NULL pointer dereference at virtual address 0038 [ 93.672809] pgd = 8007d8f22000 [ 93.672813] [0038] *pgd=0047d9123003, *pud=0047d9124003, *pmd= [ 93.672817] Intern
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
you have to build with -no-pie. Please read the Yakkety Yak opening announcement. ** Changed in: gcc-defaults (Ubuntu) Status: Confirmed => 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/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in ubuntu package in Ubuntu: Confirmed Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Aquaris E.45 OTA 10.1 Pairing does not work with Toyota Avensis (2010 model) Also does not work with Parrot Minikit portable handsfree kit (approx 10 years old) On both, entering the pairing PIN results in no action from the phone, and "pairing failed" message on the other device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574125] Re: suspend not working after upgrade
The same with kernel 4.4.0-22-generic #38-Ubuntu SMP Sun Apr 24 20:48:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux from proposed. Dell Inspiron 7548 I can't try the mainline kernel, because I need zfs and virtualbox. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: suspend not working after upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574690] fozzie (amd64) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.38/fozzie__4.4.0-22.38__2016-04-27_08-38-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574690 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-22.38 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1574690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1570195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages
[Kernel-packages] [Bug 1510134] Re: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend.
16.04 LTS is affected, too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1510134 Title: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend. Status in linux package in Ubuntu: Confirmed Bug description: ALPS touchpad and buttons work only in a single window. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jsum 1861 F pulseaudio /dev/snd/controlC1: jsum 1861 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 16:57:30 2015 HibernationDevice: RESUME=UUID=13c66e6a-58e2-431a-9f1b-15248ae2fbd0 InstallationDate: Installed on 2015-06-08 (140 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: Dell Inc. Latitude E5440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-31-generic N/A linux-backports-modules-3.19.0-31-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
Please explain how I am going to build with -no-pie when apt-get and dkms automates the entire process here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in ubuntu package in Ubuntu: Confirmed Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.la
[Kernel-packages] [Bug 1574690] fozzie (i386) - tests ran: 136, failed: 0
tests ran: 136, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-22.38/fozzie__4.4.0-22.38__2016-04-27_09-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574690 Title: linux: 4.4.0-22.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-22.38 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 -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1574690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
@David Please ask on askubuntu to get a dev answer; here it is only for report, not asking. 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/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in ubuntu package in Ubuntu: Confirmed Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.n
[Kernel-packages] [Bug 1575451] Re: PIE mode breaks building kernel modules
*** This bug is a duplicate of bug 1574982 *** https://bugs.launchpad.net/bugs/1574982 I can't run apport-collect because this is marked as a duplicate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575451 Title: PIE mode breaks building kernel modules Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-352 package in Ubuntu: New Status in nvidia-graphics-drivers-361 package in Ubuntu: New Bug description: DKMS make.log for nvidia-364-364.19 for kernel 4.4.0-22-generic (x86_64) Tue Apr 26 21:55:12 EDT 2016 make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-364/364.19/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler SYMLINK /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-kernel.o SYMLINK /var/lib/dkms/nvidia-364/364.19/build/nvidia-modeset/nv-modeset-kernel.o CONFTEST: INIT_WORK CONFTEST: remap_pfn_range CONFTEST: follow_pfn CONFTEST: vmap CONFTEST: set_pages_uc CONFTEST: set_memory_uc CONFTEST: change_page_attr CONFTEST: set_memory_array_uc CONFTEST: pci_get_class CONFTEST: pci_choose_state CONFTEST: vm_insert_page CONFTEST: acpi_device_id CONFTEST: acquire_console_sem CONFTEST: console_lock CONFTEST: kmem_cache_create CONFTEST: on_each_cpu CONFTEST: smp_call_function CONFTEST: acpi_evaluate_integer CONFTEST: ioremap_cache CONFTEST: ioremap_wc CONFTEST: acpi_walk_namespace CONFTEST: pci_domain_nr CONFTEST: pci_dma_mapping_error CONFTEST: sg_alloc_table CONFTEST: sg_init_table CONFTEST: pci_get_domain_bus_and_slot CONFTEST: get_num_physpages CONFTEST: efi_enabled CONFTEST: proc_create_data CONFTEST: pde_data CONFTEST: proc_remove CONFTEST: pm_vt_switch_required CONFTEST: drm_driver_has_set_busid CONFTEST: xen_ioemu_inject_msi CONFTEST: phys_to_dma CONFTEST: write_cr4 CONFTEST: of_parse_phandle CONFTEST: get_dma_ops CONFTEST: for_each_online_node CONFTEST: node_end_pfn CONFTEST: pci_bus_address CONFTEST: remap_page_range CONFTEST: address_space_init_once CONFTEST: kbasename CONFTEST: fatal_signal_pending CONFTEST: list_cut_position CONFTEST: hlist_for_each_entry CONFTEST: vzalloc CONFTEST: wait_on_bit_lock_argument_count CONFTEST: bitmap_clear CONFTEST: drm_dev_unref CONFTEST: drm_reinit_primary_mode_group CONFTEST: drm_atomic_set_mode_for_crtc CONFTEST: drm_atomic_clean_old_fb CONFTEST: i2c_adapter CONFTEST: pm_message_t CONFTEST: irq_handler_t CONFTEST: acpi_device_ops CONFTEST: acpi_op_remove CONFTEST: outer_flush_all CONFTEST: proc_dir_entry CONFTEST: scatterlist CONFTEST: sg_table CONFTEST: file_operations CONFTEST: vm_operations_struct CONFTEST: atomic_long_type CONFTEST: pci_save_state CONFTEST: file_inode CONFTEST: task_struct CONFTEST: kuid_t CONFTEST: dma_ops CONFTEST: dma_map_ops CONFTEST: noncoherent_swiotlb_dma_ops CONFTEST: fault_flags CONFTEST: atomic64_type CONFTEST: address_space CONFTEST: backing_dev_info CONFTEST: kernel_write CONFTEST: strnstr CONFTEST: iterate_dir CONFTEST: kstrtoull CONFTEST: get_user_pages_remote CONFTEST: drm_bus_present CONFTEST: drm_bus_has_bus_type CONFTEST: drm_bus_has_get_irq CONFTEST: drm_bus_has_get_name CONFTEST: drm_driver_has_legacy_dev_list CONFTEST: drm_crtc_state_has_connectors_changed CONFTEST: drm_init_functions_have_name_arg CONFTEST: drm_mode_connector_list_update_has_merge_type_bits_arg CONFTEST: dom0_kernel_present CONFTEST: drm_available CONFTEST: nvidia_grid_build CONFTEST: drm_atomic_available CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-frontend.o CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-instance.o CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv.o /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode /* _NVRM_COPYRIGHT_BEGIN_ ^ CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-acpi.o /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-instance.c:1:0: error: code model kernel does not support PIC mode /* _NVRM_COPYRIGHT_BEGIN_ ^ CC [M] /var/lib/dkms/nvidia-364/364.19/build/nvidia/nv-chrdev.o scripts/Makefile.build:258: recipe for target '/var/lib/dkms/nvidia-364/364.19/build/nvidia/n
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
My comment was sarcastic. The build flags for dkms packages are invisible to the end user and there is no easy way to change them. This is either a packaging error with the kernel module or the gcc default flags are erroneous. In either case this is not something the end user solves by changing build flags. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in ubuntu package in Ubuntu: Confirmed Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/+subs
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
** Package changed: ubuntu (Ubuntu) => dkms (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in dkms package in Ubuntu: Confirmed Status in gcc-defaults package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1574982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574125] Re: suspend not working after upgrade
Same here: Dell Latitude E6520 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: suspend not working after upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571667] bantam (i386) - tests ran: 13, failed: 2
tests ran: 13, failed: 2; http://kernel.ubuntu.com/testing/4.2.0-36.41/bantam__4.2.0-36.41__2016-04-27_07-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571667 Title: linux: 4.2.0-36.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-36.41 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-Prepare-package-start:Monday, 18. April 2016 13:51 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1571667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407942] Re: CVE-2014-4322
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1407942 Title: CVE-2014-4322 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in lin
[Kernel-packages] [Bug 1334989] Re: CVE-2014-4508
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1334989 Title: CVE-2014-4508 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty:
[Kernel-packages] [Bug 1335313] Re: CVE-2014-4608
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1335313 Title: CVE-2014-4608 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty:
[Kernel-packages] [Bug 1403851] Re: CVE-2014-4323
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1403851 Title: CVE-2014-4323 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty:
[Kernel-packages] [Bug 1206200] Re: CVE-2013-1060
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Description changed: A certain Ubuntu build procedure for perf, as distributed in the Linux kernel packages in Ubuntu 10.04 LTS, 12.04 LTS, 12.10, 13.04, and 13.10, sets the HOME environment variable to the ~buildd directory and consequently reads the system configuration file from the ~buildd directory, which allows local users to gain privileges by leveraging control over the buildd account. + + Break-Fix: - local-2013-1060 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1206200 Title: CVE-2013-1060 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1575611] Re: CVE-2008-2544
CVE-2008-2544 ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu
[Kernel-packages] [Bug 1575611] [NEW] CVE-2008-2544
*** This bug is a security vulnerability *** Public security bug reported: mounting proc readonly on a different mount point silently mounts it rw if the /proc mount is rw ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-wily (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-xenial (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu Vivid) Importance: Undecided Status: New ** Af
[Kernel-packages] [Bug 1252419] Re: CVE-2013-4511
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: Won't Fix ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: Won't Fix ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252419 Title: CVE-2013-4511 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: Won't Fix Status in linux-lts-backport-natty package in Ubuntu: Won't Fix Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in linux-lts-backport-maverick source package in Raring:
[Kernel-packages] [Bug 1312984] Re: CVE-2014-0077
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1312984 Title: CVE-2014-0077 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Won't Fix Status in linux-lts-backport-natty source package in Precise: Won't Fix Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Won't Fix Status in linux-lts-backport-natty source package in Quantal: Won't Fix Status in li
[Kernel-packages] [Bug 1339297] Re: CVE-2014-4653
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339297 Title: CVE-2014-4653 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1339294] Re: CVE-2014-4652
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339294 Title: CVE-2014-4652 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
@shinyblue you can try different version from ppa, but remember to turn off Nvidia in bios before you are ready to turn it on. Terminal upgrade and terminal recovery console is a very bare runtime without any power management. I was facing frequent force-reset while working in terminal, due to overheat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571667] bantam (amd64) - tests ran: 18, failed: 0
tests ran: 18, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-36.41/bantam__4.2.0-36.41__2016-04-27_11-41-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/1571667 Title: linux: 4.2.0-36.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-36.41 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-Prepare-package-start:Monday, 18. April 2016 13:51 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1571667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1339303] Re: CVE-2014-4654
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339303 Title: CVE-2014-4654 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1339306] Re: CVE-2014-4656
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339306 Title: CVE-2014-4656 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1339304] Re: CVE-2014-4655
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1339304 Title: CVE-2014-4655 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1336135] Re: CVE-2014-4667
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1336135 Title: CVE-2014-4667 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Saucy: Won't Fix Status in linux-lts-backport-natty source package in Saucy: Won't Fix Status in linux source package in Trusty: Fix Released St
[Kernel-packages] [Bug 1574125] Re: suspend not working after upgrade
Same for me on Samsung Laptop. Using former 4.2 Kernel works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: suspend not working after upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: Ubuntu 16.04 consistently freezes up / hangs
I have the same problem !! Lenovo G50-30 with Intel Pentium N3540 CPU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Incomplete Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13 bus info: pci@:00:13.0 version: 0e
[Kernel-packages] [Bug 1574801] Re: zfs posix default permissions lost on reboot or unmount
** Description changed: + [SRU Justification][XENIAL] + Commit 4967a3e introduced a typo that caused the ZPL to store the + intended default ACL as an access ACL. Due to caching this problem + may not become visible until the filesystem is remounted or the inode + is evicted from the cache. + + [FIX] + https://github.com/zfsonlinux/zfs/commit/98f03691a4c08f38ca4538c468e9523f8e6b24be + + [TESTCASE] + from https://github.com/zfsonlinux/zfs/issues/4520: + + [root@localhost ~]# cd /mnt/data/ + [root@localhost data]# mkdir test_dir + [root@localhost data]# setfacl -R --mask -m u:uadm:rwX test_dir/ + [root@localhost data]# setfacl -R -d --mask -m u:uadm:rwX test_dir/ + [root@localhost data]# getfacl test_dir/ + # file: test_dir/ + # owner: root + # group: root + user::rwx + user:uadm:rwx + group::r-x + mask::rwx + other::r-x + default:user::rwx + default:user:uadm:rwx + default:group::r-x + default:mask::rwx + default:other::r-x + + [root@localhost data]# reboot + + After a reboot without the fix one gets the following ACLs: + + [root@localhost ~]# cd /mnt/data/ + [root@localhost data]# getfacl test_dir/ + # file: test_dir/ + # owner: root + # group: root + user::rwx + user:uadm:rwx + group::r-x + mask::rwx + other::r-x + + With the fix: + + [root@localhost data]# getfacl test_dir/ + # file: test_dir/ + # owner: root + # group: root + user::rwx + user:uadm:rwx + group::r-x + mask::rwx + other::r-x + default:user::rwx + default:user:uadm:rwx + default:group::r-x + default:mask::rwx + default:other::r-x + + [REGRESSION POTENTAL] + Minimal ZFS only and touches just acl setting. This corrects just the ACL_TYPE_DEFAULT case for the ACL setting for ZFS, and sets it to the *correct* name. It is a trivial one line fix. + + -- + Ubuntu 16.04 server Problem: Posix default permissions on zfs datasets are lost after rebooting the server or unmounting/remount. See here for details and fix: https://github.com/zfsonlinux/zfs/issues/4520 - - --- + --- AlsaDevices: - total 0 - crw-rw+ 1 root audio 116, 1 Apr 24 22:44 seq - crw-rw+ 1 root audio 116, 33 Apr 24 22:44 timer + total 0 + crw-rw+ 1 root audio 116, 1 Apr 24 22:44 seq + crw-rw+ 1 root audio 116, 33 Apr 24 22:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - 0 nouveaufb - 1 astdrmfb + 0 nouveaufb + 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: - linux-restricted-modules-4.4.0-21-generic N/A - linux-backports-modules-4.4.0-21-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-21-generic N/A + linux-backports-modules-4.4.0-21-generic N/A + linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory 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: 07/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B-X series dmi.board.vendor: ASUSTeK Computer INC. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6702:bd07/23/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnP8B-Xseries:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574801 Title: zfs posix default permissions lost on reboot or unmount Status in linux package in Ubuntu: In Progress Bug description: [SRU Justification][XENIAL] Commit 4967a3e introduced a typo that caused the ZPL to store the intended d
[Kernel-packages] [Bug 1421372] Re: CVE-2014-5332
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1421372 Title: CVE-2014-5332 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty:
[Kernel-packages] [Bug 1349804] Re: CVE-2014-5077
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1349804 Title: CVE-2014-5077 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1362447] Re: CVE-2014-5471
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362447 Title: CVE-2014-5471 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1362448] Re: CVE-2014-5472
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1362448 Title: CVE-2014-5472 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."
I'm running trusty with wily kernel 4.2.0-35-generic, linux-generic-lts- wily. It's also affected by the same 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/1483214 Title: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc." Status in linux package in Ubuntu: Fix Released Status in openipmi package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Released Status in openipmi source package in Vivid: Invalid Bug description: Hello, after upgrading my system to 14.04.3 LTS and installing the Vivid-LTS- Enablement-Stack the kernel log of my system is spammed with the following message by the "impi_si" kernel module: ... [ 2268.244383] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2269.451974] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2270.252290] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2271.452749] ipmi_si 00:05: Could not set the global enables: 0xcc. [ 2272.253057] ipmi_si 00:05: Could not set the global enables: 0xcc. ... This bug is already known to the ipmi_si kernel module maintainer and seems to be fixed in 4.0+ kernels. Is it possible to backport this fix to the Vivid 3.19 kernel? Please see this mail thread: https://www.mail-archive.com/openipmi- develo...@lists.sourceforge.net/msg02425.html IPMI functionality seems to be unaffected by this bug but as I said it spams the kernel log and that is rather annoying. System information: lsb_release -rd: Description:Ubuntu 14.04.3 LTS Release:14.04 apt-cache policy openipmi: openipmi: Installiert: 2.0.18-0ubuntu7.1 Installationskandidat: 2.0.18-0ubuntu7.1 Versionstabelle: *** 2.0.18-0ubuntu7.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.18-0ubuntu7 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Greetings, Felix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574801] Re: zfs posix default permissions lost on reboot or unmount
Patch sent to mailing list for review: https://lists.ubuntu.com/archives /kernel-team/2016-April/076790.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/1574801 Title: zfs posix default permissions lost on reboot or unmount Status in linux package in Ubuntu: In Progress Bug description: [SRU Justification][XENIAL] Commit 4967a3e introduced a typo that caused the ZPL to store the intended default ACL as an access ACL. Due to caching this problem may not become visible until the filesystem is remounted or the inode is evicted from the cache. [FIX] https://github.com/zfsonlinux/zfs/commit/98f03691a4c08f38ca4538c468e9523f8e6b24be [TESTCASE] from https://github.com/zfsonlinux/zfs/issues/4520: [root@localhost ~]# cd /mnt/data/ [root@localhost data]# mkdir test_dir [root@localhost data]# setfacl -R --mask -m u:uadm:rwX test_dir/ [root@localhost data]# setfacl -R -d --mask -m u:uadm:rwX test_dir/ [root@localhost data]# getfacl test_dir/ # file: test_dir/ # owner: root # group: root user::rwx user:uadm:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:uadm:rwx default:group::r-x default:mask::rwx default:other::r-x [root@localhost data]# reboot After a reboot without the fix one gets the following ACLs: [root@localhost ~]# cd /mnt/data/ [root@localhost data]# getfacl test_dir/ # file: test_dir/ # owner: root # group: root user::rwx user:uadm:rwx group::r-x mask::rwx other::r-x With the fix: [root@localhost data]# getfacl test_dir/ # file: test_dir/ # owner: root # group: root user::rwx user:uadm:rwx group::r-x mask::rwx other::r-x default:user::rwx default:user:uadm:rwx default:group::r-x default:mask::rwx default:other::r-x [REGRESSION POTENTAL] Minimal ZFS only and touches just acl setting. This corrects just the ACL_TYPE_DEFAULT case for the ACL setting for ZFS, and sets it to the *correct* name. It is a trivial one line fix. -- Ubuntu 16.04 server Problem: Posix default permissions on zfs datasets are lost after rebooting the server or unmounting/remount. See here for details and fix: https://github.com/zfsonlinux/zfs/issues/4520 --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Apr 24 22:44 seq crw-rw+ 1 root audio 116, 33 Apr 24 22:44 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 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: Error: [Errno 2] No such file or directory 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: 07/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B-X series dmi.board.vendor: ASUSTeK Computer INC. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6702:bd07/23/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnP8B-Xseries:rvr:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575651] [NEW] X stops responding to input on power saving mode
You have been subscribed to a public bug: Once my session has been locked and the screen off, Xserver stops responding to input ( I can still move the cursor). I can re-activate it by typing in a tty "xset dpms force on". If I just lock the screen all works fine. If I just turn off the monitor (xset dpms force off) all works fine. The same system (kubuntu 16.04 64bit) on different hardware (nvidia) has no problem. The issue does NOT occur when running this kernel: - linux-image-4.6.0-996-generic (4.6.0-996.201604262201) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 27 14:00:52 2016 InstallationDate: Installed on 2016-04-27 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kde xenial -- X stops responding to input on power saving mode https://bugs.launchpad.net/bugs/1575651 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575651] Re: X stops responding to input on power saving mode
** Description changed: Once my session has been locked and the screen off, Xserver stops responding to input ( I can still move the cursor). I can re-activate it by typing in a tty "xset dpms force on". If I just lock the screen all works fine. If I just turn off the monitor (xset dpms force off) all works fine. The same system (kubuntu 16.04 64bit) on different hardware (nvidia) has no problem. - Symptoms: - After waking the screen from power saving/screensaver, the primary display wakes but X stops responding to input (the mouse cursor can still move, but clicking has no effect). Secondary display does not wake. - No errors in dmesg - - Frequency/conditions: - Occurs almost every time the screen enters power saving + locked (possibly DPMS issue?) - - VGA: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 - Series] (APU AMD Athlon 5350) + The issue does NOT occur when running this kernel: + - linux-image-4.6.0-996-generic (4.6.0-996.201604262201) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 27 14:00:52 2016 InstallationDate: Installed on 2016-04-27 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) ** Package changed: xserver-xorg-video-ati (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575651 Title: X stops responding to input on power saving mode Status in linux package in Ubuntu: New Bug description: Once my session has been locked and the screen off, Xserver stops responding to input ( I can still move the cursor). I can re-activate it by typing in a tty "xset dpms force on". If I just lock the screen all works fine. If I just turn off the monitor (xset dpms force off) all works fine. The same system (kubuntu 16.04 64bit) on different hardware (nvidia) has no problem. The issue does NOT occur when running this kernel: - linux-image-4.6.0-996-generic (4.6.0-996.201604262201) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 27 14:00:52 2016 InstallationDate: Installed on 2016-04-27 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
I can confirm this bug is only triggered when the machine got 2-3GB RAM or less. I got two identical machines running Ubuntu 16.04. One got 8Gb of RAM and on this machine kswapd0 doesn't deadlock at 100% CPU Usage. On my 2GB RAM machine the issue is worse than under Ubuntu 15.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1370042] Re: CVE-2014-6410
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370042 Title: CVE-2014-6410 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1575274] Re: System Crash during 16.04 Upgrade from 14.04
@MeadeBaron any chance this machine has an Nvidia card? Had a similar issue on one of my hosts with Nvidia. I was able to boot into an older kernel from the Grub boot menu and upgraded the Nvidia driver from 340 to 361. Then the 4.4.0-21 kernel(current as of this post), would boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575274 Title: System Crash during 16.04 Upgrade from 14.04 Status in linux package in Ubuntu: Confirmed Bug description: I was upgrading 2 machines from Trusty to Xenial. I had success on my laptop...but had a system crash on my main machine running Ubuntu- Studio 14.04. I have tried creating LIVE-USB's to reboot and repair the install...but to no avail. No matter what I do I arrive at the same "Call Trace" and "end Kernel panic - not syncing: Attempted to kill init! exit code=0x7f00" message. The system freezes at that point and there is absolutely no forward movement from there. HELP! My machine is completely crashed...I believe this is Ubuntu's answer to the "Windows Blue Screen of Death". Please advise how I can repair my Ubuntu Studio 16.04 installation. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1370046] Re: CVE-2014-6417
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370046 Title: CVE-2014-6417 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-i
[Kernel-packages] [Bug 1370044] Re: CVE-2014-6416
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370044 Title: CVE-2014-6416 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-i
[Kernel-packages] [Bug 1392006] Re: CVE-2014-7825
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392006 Title: CVE-2014-7825 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1416498] Re: CVE-2014-7822
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1416498 Title: CVE-2014-7822 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1370047] Re: CVE-2014-6418
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1370047 Title: CVE-2014-6418 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-i
[Kernel-packages] [Bug 1575651] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1575651 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575651 Title: X stops responding to input on power saving mode Status in linux package in Ubuntu: Incomplete Bug description: Once my session has been locked and the screen off, Xserver stops responding to input ( I can still move the cursor). I can re-activate it by typing in a tty "xset dpms force on". If I just lock the screen all works fine. If I just turn off the monitor (xset dpms force off) all works fine. The same system (kubuntu 16.04 64bit) on different hardware (nvidia) has no problem. The issue does NOT occur when running this kernel: - linux-image-4.6.0-996-generic (4.6.0-996.201604262201) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-radeon 1:7.7.0-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 27 14:00:52 2016 InstallationDate: Installed on 2016-04-27 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559784] Re: zFCP on s390x problems on zfcp module unloading
** Changed in: linux (Ubuntu) Milestone: xenial-updates => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559784 Title: zFCP on s390x problems on zfcp module unloading Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Right after unloading zFCP module I got: [ 1432.522123] sysfs group 00b5aa30 not found for kobject '1:0:0:1073823786' [ 1432.522138] [ cut here ] [ 1432.522139] WARNING: at /build/linux-RgAt0H/linux-4.3.0/fs/sysfs/group.c:224 [ 1432.522140] Modules linked in: ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) vmur(E) qeth_l2(E) qeth(E) ccwgroup(E) dasd_eckd_mod(E) dasd_mod(E) zfcp(E-) qdio(E) scsi_transport_fc(E) [ 1432.522149] CPU: 2 PID: 5873 Comm: rmmod Tainted: GE 4.3.0-2-generic #11-Ubuntu [ 1432.522151] task: 76f4a9e0 ti: ed85c000 task.ti: ed85c000 [ 1432.522152] Krnl PSW : 0704d0018000 0036cbee (sysfs_remove_group+0xbe/0xd0) [ 1432.522158]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3 Krnl GPRS: 00c76c33 00c58e3c 0045 fb1ac7a0 [ 1432.522160]0036cbea 78d70050 78d7 [ 1432.522161]8000 f93df000 78d7e010 [ 1432.522162]ed85c000 00b5aa30 0036cbea ed85fa78 [ 1432.522168] Krnl Code: 0036cbde: c020002bc358 larl %r2,8e528e 0036cbe4: c0e5fff7144a brasl %r14,24f478 #0036cbea: a7f40001 brc 15,36cbec >0036cbee: e340f0c4 lg %r4,192(%r15) 0036cbf4: ebaff0a4 lmg %r10,%r15,160(%r15) 0036cbfa: 07f4 bcr 15,%r4 0036cbfc: 0707 bcr 0,%r7 0036cbfe: 0707 bcr 0,%r7 [ 1432.522177] Call Trace: [ 1432.522179] ([<0036cbea>] sysfs_remove_group+0xba/0xd0) [ 1432.522183] [<00575a44>] device_del+0x5c/0x268 [ 1432.522184] [<00575c90>] device_unregister+0x40/0x98 [ 1432.522186] [<004d9b0c>] bsg_unregister_queue+0x74/0xd8 [ 1432.522189] [<005aff76>] __scsi_remove_device+0xe6/0x118 [ 1432.522192] [<005adaca>] scsi_forget_host+0xca/0xf8 [ 1432.522193] [<0059fa86>] scsi_remove_host+0xbe/0x1c8 [ 1432.522200] [<03ff800496a6>] zfcp_scsi_adapter_unregister+0x9e/0xc8 [zfcp] [ 1432.522202] [<03ff8003b55e>] zfcp_adapter_unregister+0x7e/0xc0 [zfcp] [ 1432.522205] [<03ff8003c876>] zfcp_ccw_remove+0x28e/0x2b0 [zfcp] [ 1432.522207] [<00604814>] ccw_device_remove+0x44/0x210 [ 1432.522209] [<0057a9fe>] __device_release_driver+0xa6/0x150 [ 1432.522211] [<0057b782>] driver_detach+0x11a/0x120 [ 1432.522212] [<0057a342>] bus_remove_driver+0x82/0x118 [ 1432.522214] [<03ff8004bdd2>] zfcp_module_exit+0x2a/0x258 [zfcp] [ 1432.522217] [<001caf6c>] SyS_delete_module+0x1c4/0x210 [ 1432.51] [<0076dbfe>] system_call+0xd6/0x264 [ 1432.52] [<03ffb0f6e416>] 0x3ffb0f6e416 [ 1432.53] Last Breaking-Event-Address: [ 1432.54] [<0036cbea>] sysfs_remove_group+0xba/0xd0 [ 1432.55] ---[ end trace 2e7b1c668b02f90a ]--- [ 1432.522430] sysfs group 00b5aa30 not found for kobject '1:0:0:1073823786' [ 1432.522434] [ cut here ] Opening the bug for tracking purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1383358] Re: CVE-2014-7975
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1383358 Title: CVE-2014-7975 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1383356] Re: CVE-2014-7970
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1383356 Title: CVE-2014-7970 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1430949] Re: CVE-2014-8172
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1430949 Title: CVE-2014-8172 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in lin
[Kernel-packages] [Bug 1413741] Re: CVE-2014-8159
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1413741 Title: CVE-2014-8159 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linu
[Kernel-packages] [Bug 1448291] Re: CVE-2014-8171
** Also affects: linux (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Low Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Low Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Low Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Low Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1448291 Title: CVE-2014-8171 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status i
[Kernel-packages] [Bug 1575706] Re: CVE-2016-2187
CVE-2016-2187 ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Yakkety) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu
[Kernel-packages] [Bug 1575706] [NEW] CVE-2016-2187
*** This bug is a security vulnerability *** Public security bug reported: Kernel panic on invalid USB device descriptor (gtco driver) ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-wily (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-xenial (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-saucy (Ubuntu Vivid)
[Kernel-packages] [Bug 1413109] Re: CVE-2014-8160
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1413109 Title: CVE-2014-8160 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source
[Kernel-packages] [Bug 1392008] Re: CVE-2014-7826
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392008 Title: CVE-2014-7826 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linu
[Kernel-packages] [Bug 1403852] Re: CVE-2014-8133
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1403852 Title: CVE-2014-8133 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1392820] Re: CVE-2014-7841
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392820 Title: CVE-2014-7841 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1392013] Re: CVE-2014-8709
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392013 Title: CVE-2014-8709 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Released Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1400314] Re: CVE-2014-8134
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1400314 Title: CVE-2014-8134 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invali
[Kernel-packages] [Bug 1388975] Re: CVE-2014-8559
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1388975 Title: CVE-2014-8559 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1403855] Re: CVE-2014-9322
** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: High Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: High Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: High Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: High Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1403855 Title: CVE-2014-9322 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linu
[Kernel-packages] [Bug 1398795] Re: CVE-2014-9090
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Fix Released ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1398795 Title: CVE-2014-9090 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
In the earliest linked report of this bug the deadlock occured also with 8GB RAM (and still the case in 15.10). Will test 16.04 later when it stabilizes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407945] Re: CVE-2014-9419
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1407945 Title: CVE-2014-9419 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source packa
[Kernel-packages] [Bug 1409048] Re: CVE-2014-9529
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1409048 Title: CVE-2014-9529 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source
[Kernel-packages] [Bug 1395189] Re: CVE-2014-8989
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-fsl-imx51 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mvl-dove (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ec2 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-ti-omap4 (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-backport-maverick (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-armadaxp (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-quantal (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-raring (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-saucy (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-mako (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-manta (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-goldfish (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-flo (Ubuntu Yakkety) Importance: Medium Status: New ** Also affects: linux-lts-trusty (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-utopic (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-vivid (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-lts-wily (Ubuntu Yakkety) Importance: Medium Status: Invalid ** Also affects: linux-raspi2 (Ubuntu Yakkety) Importance: Medium Status: Fix Committed ** Also affects: linux-lts-xenial (Ubuntu Yakkety) Importance: Medium Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1395189 Title: CVE-2014-8989 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Sta
[Kernel-packages] [Bug 1575711] [NEW] package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot
Public bug reported: Partial upgrade failed. package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-25-generic 4.2.0-25.30 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1721 F pulseaudio /dev/snd/controlC0: stephen1721 F pulseaudio Date: Wed Apr 27 07:36:35 2016 DpkgHistoryLog: Start-Date: 2016-04-27 07:36:26 Upgrade: oxideqt-codecs:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), firefox-locale-en:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), firefox:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), liboxideqtcore0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqtquick0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqt-qmlplugin:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), docker-engine:amd64 (1.11.0-0~wily, 1.11.1-0~wily) DuplicateSignature: package:linux-image-extra-4.2.0-25-generic:4.2.0-25.30:package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3b90a5f2-f4d2-4642-a833-3b8fe62b8b05 InstallationDate: Installed on 2015-10-23 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: Notebook P7xxDM(-G) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=UUID=eb9c58d3-5ba8-43d9-b8df-af22b7e4076e ro quiet splash nomodeset vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P7xxDM(-G) dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2015:svnNotebook:pnP7xxDM(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: P7xxDM(-G) dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575711 Title: package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: Partial upgrade failed. package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-25-generic 4.2.0-25.30 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1721 F pulseaudio /dev/snd/controlC0: stephen1721 F pulseaudio Date: Wed Apr 27 07:36:35 2016 DpkgHistoryLog: Start-Date: 2016-04-27 07:36:26 Upgrade: oxideqt-codecs:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), firefox-locale-en:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), firefox:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), liboxideqtcore0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqtquick0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqt-qmlplugin:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.
[Kernel-packages] [Bug 1575711] Re: package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot c
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575711 Title: package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: New Bug description: Partial upgrade failed. package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-25-generic 4.2.0-25.30 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1721 F pulseaudio /dev/snd/controlC0: stephen1721 F pulseaudio Date: Wed Apr 27 07:36:35 2016 DpkgHistoryLog: Start-Date: 2016-04-27 07:36:26 Upgrade: oxideqt-codecs:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), firefox-locale-en:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), firefox:amd64 (45.0.2+build1-0ubuntu0.15.10.1, 46.0+build5-0ubuntu0.15.10.2), liboxideqtcore0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqtquick0:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), liboxideqt-qmlplugin:amd64 (1.13.6-0ubuntu0.15.10.1, 1.14.7-0ubuntu0.15.10.1), docker-engine:amd64 (1.11.0-0~wily, 1.11.1-0~wily) DuplicateSignature: package:linux-image-extra-4.2.0-25-generic:4.2.0-25.30:package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3b90a5f2-f4d2-4642-a833-3b8fe62b8b05 InstallationDate: Installed on 2015-10-23 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: Notebook P7xxDM(-G) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-35-generic.efi.signed root=UUID=eb9c58d3-5ba8-43d9-b8df-af22b7e4076e ro quiet splash nomodeset vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.2.0-25-generic 4.2.0-25.30 failed to install/upgrade: package linux-image-extra-4.2.0-25-generic is not ready for configuration cannot configure (current status 'half-installed') UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P7xxDM(-G) dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2015:svnNotebook:pnP7xxDM(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: P7xxDM(-G) dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649084/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13
[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs
I did wonder if it was a driver issue related to my processor, so that or a kernel issue makes sense. Not sure how to confirm that though. In the additional drivers thingy it says it is using a backport driver for something that i assume is processor related. My understanding was that backport drivers are unstable and should not be used unless absolutely necessary. There was also a processor microcode firmware proprietary driver that was not being used, so i tried it to see if that would fix the problem, it did not. I will try to do the apport log thing that the automatic script suggested. Hopefully you guy's can figure this out as this is a pretty serious issue. Let me know if you need any more logs. It sounds like the other guy with the same processor as my laptop does also has the same problem. ** Attachment added: "Screenshot from 2016-04-27 08-42-04.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4649080/+files/Screenshot%20from%202016-04-27%2008-42-04.png ** Tags added: apport-collected xenial ** Description changed: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series G
[Kernel-packages] [Bug 1575467] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649092/+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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physica
[Kernel-packages] [Bug 1575467] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649086/+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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id
[Kernel-packages] [Bug 1575467] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649085/+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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13
[Kernel-packages] [Bug 1575467] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649090/+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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13
[Kernel-packages] [Bug 1575467] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649088/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical
[Kernel-packages] [Bug 1575467] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649094/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13
[Kernel-packages] [Bug 1575467] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649096/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id: 13
[Kernel-packages] [Bug 1575467] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1575467/+attachment/4649091/+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/1575467 Title: Ubuntu 16.04 consistently freezes up / hangs Status in linux package in Ubuntu: Confirmed Bug description: Not sure what package this is related to. My best guess is Unity, but i honestly have no idea. After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron laptop consistently freezes up and is unresponsive 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. So i wonder if this has something to do with my memory buffer or something. It seems to happen more often in Google Chrome than Firefox, but it happens with both. I know Google Chrome uses more memory though. And it has happened at least once with no videos loaded, so i doubt it's some sort of weird flash issue. 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. I will try to upload any log files that people think may be useful. I will see if i can do the recommended ssh monitoring method while trying to reproduce it to see if i can see an error that way. Not sure if this hardware info helps: lspci reports: 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e) 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e) 00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA AHCI Controller (rev 0e) 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e) 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e) 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e) 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e) 03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) andrew@andrew-Inspiron-3451:~$ sudo lshw andrew-inspiron-3451 description: Computer width: 64 bits capabilities: smbios-2.8 vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3834MiB *-cpu product: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 909MHz capacity: 2665MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat cpufreq *-pci description: Host bridge product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0e width: 32 bits clock: 33MHz configuration: driver=iosf_mbi_pci resources: irq:0 *-display description: VGA compatible controller product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0e width: 32 bits clock: 33MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:89 memory:d000-d03f memory:c000-cfff ioport:f080(size=8) *-storage description: SATA controller product: Atom Processor E3800 Series SATA AHCI Controller vendor: Intel Corporation physical id:
