[Kernel-packages] [Bug 1640028] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640028 Title: fsck or initramfs not working Status in linux package in Ubuntu: Confirmed Bug description: when I boot get to initramfs, when i type exit i get the following error. ata1: failed command READ FDMA QUEDED. Kenerl panic. Kernel offset :disable ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4323 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Tue Nov 8 06:07:36 2016 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0120.2013.1112.1412 dmi.board.name: DH61SA dmi.board.vendor: Intel Corporation dmi.board.version: AAG38870-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0120.2013.1112.1412:bd11/12/2013:svn:pn:pvr:rvnIntelCorporation:rnDH61SA:rvrAAG38870-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640028] [NEW] fsck or initramfs not working
Public bug reported: when I boot get to initramfs, when i type exit i get the following error. ata1: failed command READ FDMA QUEDED. Kenerl panic. Kernel offset :disable ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4323 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Tue Nov 8 06:07:36 2016 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0120.2013.1112.1412 dmi.board.name: DH61SA dmi.board.vendor: Intel Corporation dmi.board.version: AAG38870-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0120.2013.1112.1412:bd11/12/2013:svn:pn:pvr:rvnIntelCorporation:rnDH61SA:rvrAAG38870-201:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640028 Title: fsck or initramfs not working Status in linux package in Ubuntu: New Bug description: when I boot get to initramfs, when i type exit i get the following error. ata1: failed command READ FDMA QUEDED. Kenerl panic. Kernel offset :disable ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4323 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Tue Nov 8 06:07:36 2016 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0120.2013.1112.1412 dmi.board.name: DH61SA dmi.board.vendor: Intel Corporation dmi.board.version: AAG38870-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0120.2013.1112.1412:bd11/12/2013:svn:pn:pvr:rvnIntelCorporation:rnDH61SA:rvrAAG38870-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec
I've Dell 5000 Series, And sound card model is ALC3234, In that laptop, When I plug the headset, A dialogue is a popup, Unknown Audio device(see the attachment), Then, When I select Headset, the headset is working, Likewise, Can't you give us a fix like that? ** Attachment added: "rr.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447909/+attachment/4774281/+files/rr.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447909 Title: external mic not detected on machines with alc256 codec Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This bug is used for tracking, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1447909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639961] Re: NMI watchdog: BUG: soft lockup during KVM guest migration test suite
** Tags removed: bugnameltc-146681 severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639961 Title: NMI watchdog: BUG: soft lockup during KVM guest migration test suite Status in linux package in Ubuntu: New Bug description: Hello Canonical. We would like the changes in Commit 8117ac6a6c2f pulled into the Ubuntu 16.10 stream to address the following issue: == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 == ---Problem Description--- Softlock up and call trace observed from libvirtd during guest migration test suite ---uname output--- # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] message is continuous and recovered the machine with reboot 84050.059159] INFO: rcu_sched self-detected stall on CPU [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 softirq=549845/07 fqs=2176 [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484) [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] [84104.509395] INFO: rcu_sched self-detected stall on CPU [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 softirq=562249/562249 fqs=2364 [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351) [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56627] [84163.387536] INFO: rcu_sched self-detected stall on CPU [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=2354 [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297) [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56633] [84226.401597] INFO: rcu_sched self-detected stall on CPU [84226.401769]24-...: (21004 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=9697 [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145) [84289.415706] INFO: rcu_sched self-detected stall on CPU [84289.415879]24-...: (36758 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=16889 [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499) [84352.429857] INFO: rcu_sched self-detected stall on CPU [84352.430038]24-...: (52512 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=23975 [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027) [84415.444044] INFO: rcu_sched self-detected stall on CPU [84415.444222]24-...: (68266 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=31005 [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554) [84478.458262] INFO: rcu_sched self-detected stall on CPU [84478.458421]24-...: (84020 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=38023 [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030) [84541.472510] INFO: rcu_sched self-detected stall on CPU [84541.472680]24-...: (99774 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=45068 [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512) [84604.486783] INFO: rcu_sched self-detected stall on CPU Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636330] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2016-11-07 23:35 EDT--- cde00 (cdead...@us.ibm.com) deleted native attachment kern.log.powerio-le12.oct12 on 2016-11-07 22:24:41 cde00 (cdead...@us.ibm.com) added native attachment /tmp/AIXOS05483833/kern.log.powerio-le12.oct12 on 2016-11-07 22:24:44 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Released Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620741] Re: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620741 Title: Xubuntu 16.04 on HP Compaq nx6325 hangs on Shutdown Status in linux package in Ubuntu: Expired Bug description: $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 Have changed /etc/default/grub to attempt a fix without success... (grub.ref was original grub) :/etc/default$ grep CMDLINE grub* grub.ref:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" grub.ref:GRUB_CMDLINE_LINUX="forcepae" grub:GRUB_CMDLINE_LINUX_DEFAULT="acpi=noirq debug=y" grub:GRUB_CMDLINE_LINUX="forcepae" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xfce4-panel 4.12.0-3ubuntu2 Uname: Linux 4.6.0-040600-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Tue Sep 6 18:16:30 2016 ExecutablePath: /usr/bin/xfce4-panel InstallationDate: Installed on 2016-08-16 (21 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-08-16 (21 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) NonfreeKernelModules: wl Package: linux (not installed) Tags: xenial Uname: Linux 4.6.0-040600-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638779] Re: [arm] Missing AHCI driver in Ubuntu Xenial Installer for ARM
To solve this issue, need to integrate content of the pool/main/l/linux /sata-modules-4.8.0-26-generic-di_4.8.0-26.28_arm64.udeb package into initrd.gz. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638779 Title: [arm] Missing AHCI driver in Ubuntu Xenial Installer for ARM Status in linux package in Ubuntu: Incomplete Bug description: Download the media installation ISO file at https://www.ubuntu.com/download/server/arm and burn it to a CD-ROM. Then, put it into the SATA CD drive to install Ubuntu into Mustang/Merlin boards (XGene platform), the Installer does not detect the CD-ROM so it report a dialog with below content: "Your installation CD-ROM couldn't be mounted. This probably means that the CD-ROM was not in the drive. If so you can insert it and try again. Retry mounting the CD-ROM?". Investigate more on the installer media, I found that the AHCI driver is not enabled. Below steps I have done to check: - Mount ISO file and copy initrd.gz: # mkdir mnt # mount -o loop ubuntu-16.04.1-server-arm64.iso ./mnt # cp ./mnt/install/initrd.gz . - Extract initrd.gz: # gunzip initrd.gz # cpio -id < initrd - List the drivers/ata folder # ls lib/modules/4.4.0-31-generic/kernel/drivers block gpio gpu hid i2c input media mfd power regulator rtc usb video No lib/modules/4.4.0-31-generic/kernel/drivers/ata folder exist. Try to check with x86 installer media: # ls lib/modules/4.4.0-31-generic/kernel/drivers/ ata block char firewire gpio gpu hid hv i2c infiniband input media mfd net parport pcmcia power regulator rtc scsi tty usb video # lib/modules/4.4.0-31-generic/kernel/drivers/ata/ | grep ahci acard-ahci.ko ahci.ko ahci_platform.ko libahci.ko libahci_platform.ko Can you help to add AHCI support for Ubuntu ARM Media installer? Thanks, Thang Q. Nguyen PS: I submitted bug at https://bugs.launchpad.net/santacruz/+bug/1632559 but Thad asked to report here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640000] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/164 Title: kidle_inject overly onerous, fans never used on MacBookPro12,1 Status in linux package in Ubuntu: Confirmed Bug description: At least since upgrading to Yakkey, my MacBookPro12,1 (13", 2015) seems to respond to increased system heat using only kidle_inject, and not the built-in fan. kidle_inject with kick in rather quickly, especially with the Australian summer starting to be felt, and will render the system near useless. Doing some investigation, it appears that no fan is registered as a cooling device: > mjg@payens:~$ grep . /sys/class/thermal/cooling_device*/type > /sys/class/thermal/cooling_device0/type:Processor > /sys/class/thermal/cooling_device1/type:Processor > /sys/class/thermal/cooling_device2/type:Processor > /sys/class/thermal/cooling_device3/type:Processor > /sys/class/thermal/cooling_device4/type:intel_powerclamp Even though one is picked up by applesmc: > Nov 08 10:08:56 payens kernel: applesmc: key=670 fan=1 temp=35 index=34 acc=0 lux=2 kbd=1 The fan seems to be physically in good condition, I tested it out using the following: > root@payens:~# echo 6000 > /sys/devices/platform/applesmc.768/fan1_min Which started it blowing a lot of warm air out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.26.35 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjg3076 F pulseaudio /dev/snd/controlC0: mjg3076 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 13:36:01 2016 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (475 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor i915.fastboot=1 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-05 (33 days ago) dmi.bios.date: 09/28/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B14.1509281135 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640000] Re: kidle_inject overly onerous, fans never used on MacBookPro12, 1
Similarly to Bug #1389077, I can disable Intel Powerclamp by `rmmod intel_powerclamp` to prevent kidle_inject from being used, and in this case applesmc (presumably) will start the fan kicking in as the system gets hotter. However unlike Bug #1389077, when intel_powerclamp is loaded here the fan never seems to get used. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/164 Title: kidle_inject overly onerous, fans never used on MacBookPro12,1 Status in linux package in Ubuntu: Confirmed Bug description: At least since upgrading to Yakkey, my MacBookPro12,1 (13", 2015) seems to respond to increased system heat using only kidle_inject, and not the built-in fan. kidle_inject with kick in rather quickly, especially with the Australian summer starting to be felt, and will render the system near useless. Doing some investigation, it appears that no fan is registered as a cooling device: > mjg@payens:~$ grep . /sys/class/thermal/cooling_device*/type > /sys/class/thermal/cooling_device0/type:Processor > /sys/class/thermal/cooling_device1/type:Processor > /sys/class/thermal/cooling_device2/type:Processor > /sys/class/thermal/cooling_device3/type:Processor > /sys/class/thermal/cooling_device4/type:intel_powerclamp Even though one is picked up by applesmc: > Nov 08 10:08:56 payens kernel: applesmc: key=670 fan=1 temp=35 index=34 acc=0 lux=2 kbd=1 The fan seems to be physically in good condition, I tested it out using the following: > root@payens:~# echo 6000 > /sys/devices/platform/applesmc.768/fan1_min Which started it blowing a lot of warm air out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.26.35 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjg3076 F pulseaudio /dev/snd/controlC0: mjg3076 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 13:36:01 2016 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (475 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor i915.fastboot=1 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-05 (33 days ago) dmi.bios.date: 09/28/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B14.1509281135 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640000] [NEW] kidle_inject overly onerous, fans never used on MacBookPro12, 1
Public bug reported: At least since upgrading to Yakkey, my MacBookPro12,1 (13", 2015) seems to respond to increased system heat using only kidle_inject, and not the built-in fan. kidle_inject with kick in rather quickly, especially with the Australian summer starting to be felt, and will render the system near useless. Doing some investigation, it appears that no fan is registered as a cooling device: > mjg@payens:~$ grep . /sys/class/thermal/cooling_device*/type > /sys/class/thermal/cooling_device0/type:Processor > /sys/class/thermal/cooling_device1/type:Processor > /sys/class/thermal/cooling_device2/type:Processor > /sys/class/thermal/cooling_device3/type:Processor > /sys/class/thermal/cooling_device4/type:intel_powerclamp Even though one is picked up by applesmc: > Nov 08 10:08:56 payens kernel: applesmc: key=670 fan=1 temp=35 index=34 acc=0 lux=2 kbd=1 The fan seems to be physically in good condition, I tested it out using the following: > root@payens:~# echo 6000 > /sys/devices/platform/applesmc.768/fan1_min Which started it blowing a lot of warm air out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.26.35 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjg3076 F pulseaudio /dev/snd/controlC0: mjg3076 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 13:36:01 2016 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (475 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor i915.fastboot=1 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-05 (33 days ago) dmi.bios.date: 09/28/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B14.1509281135 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/164 Title: kidle_inject overly onerous, fans never used on MacBookPro12,1 Status in linux package in Ubuntu: New Bug description: At least since upgrading to Yakkey, my MacBookPro12,1 (13", 2015) seems to respond to increased system heat using only kidle_inject, and not the built-in fan. kidle_inject with kick in rather quickly, especially with the Australian summer starting to be felt, and will render the system near useless. Doing some investigation, it appears that no fan is registered as a cooling device: > mjg@payens:~$ grep . /sys/class/thermal/cooling_device*/type > /sys/class/thermal/cooling_device0/type:Processor > /sys/class/thermal/cooling_device1/type:Processor > /sys/class/thermal/cooling_device2/type:Processor > /sys/class/thermal/cooling_device3/type:Processor > /sys/class/thermal/cooling_device4/type:intel_powerclamp Even though one is picked up by applesmc: > Nov 08 10:08:56 payens kernel: applesmc: key=670 fan=1 temp=35 index=34 acc=0 lux=2 kbd=1 The fan seems to be physically in good condition, I tested it out using the following: > root@payens:~# echo 6000 > /sys/devices/platform/applesmc.768/fan1_min Which started it blowing a lot of warm air out. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-generic 4.8.0.26.35 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mjg3076 F pulseaudio /dev/snd/controlC0: mjg3076 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 13:36:0
[Kernel-packages] [Bug 1441852] Re: [HP Spectre x360 - 13-4010ca] Audio broken, broadwell-U audio controller
Sorry for the delay Chris (penalvch), I finally got back to my Linux partition. I noticed rc4 was released, so I downloaded and installed that and sound works! (wifi is still busted and I got some form of dkms apport "kernel is not supported" error when installing the deb, but that's beside the point... Again sorry for being unspecific, but having to reboot to post means a lot of detail gets lost...) If this bug is finally fixed I'll be able to use my Linux partition much more :) Thanks for following this me-again and penalvch! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1441852 Title: [HP Spectre x360 - 13-4010ca] Audio broken, broadwell-U audio controller Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Status in Gentoo Linux: New Bug description: On ubuntu trusty, Audio driver on HP Spectre x360 doesn't work. May be related to the bug found on the 2015 XPS 13. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446) On the kernel 4.0-rc4+ given as solution for the bug found on the XPS 13, the dmesg -t | egrep "(audio|snd|INT3438)" command return: dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0 snd_hda_intel :00:03.0: enabling device ( -> 0002) sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered --- ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isatis 1479 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1e13c664-5747-48ed-942c-18c0610b50dd InstallationDate: Installed on 2015-04-01 (12 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Spectre x360 Convertible 13 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed root=UUID=70117e8f-97a5-40f7-90fd-aa25fdba1bba ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8 RelatedPackageVersions: linux-restricted-modules-3.16.0-34-generic N/A linux-backports-modules-3.16.0-34-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 802D dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd02/05/2015:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Spectre x360 Convertible 13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Oh, and I have found this: http://linux.dell.com/files/ubuntu/precise/12.04-OSP1/ but it is Ubuntu 12.04, probably good for study purposes, not sure I would want using 4-years old OS ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Peter, thank for clarifying things for me, I appreciate it. Also, have you tried the http://linux.dell.com/ ? It's kind of unofficial dell Linux support site. Or so they say ... >> Would it be illegal to release it?? Its open source anyway. :/ Sure, Ubuntu is open source, not sure if you can take parts of Ubuntu, change it and claim it proprietary. After all, I never read the license ... :) Anyway, I don't think they would make much fuss about it. So, just give it to us, please ... ;) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]
I installed kernel 4.8.6 and it's working normally for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1595765 Title: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Status in rtl8812au package in Ubuntu: Confirmed Bug description: error update for kernel 4.7 RC 3 ProblemType: Package DistroRelease: elementary 0.4 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu] Uname: Linux 4.6.2-040602-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.7.0-040700rc3-generic Date: Thu Jun 23 22:03:59 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function) InstallationDate: Installed on 2016-06-14 (9 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613) PackageVersion: 6.30.223.248+bdcom-0ubuntu8 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1614565] Comment bridged from LTC Bugzilla
--- Comment From sarah.han...@us.ibm.com 2016-11-07 17:40 EDT---
Lata informed me that she was not able to reproduce this bug. Closing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1614565
Title:
ISST-LTE:pKVM311:lotg5:Ubutu16041:lotg5 crashed @
writeback_sb_inodes+0x30c/0x590
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Bug description:
== Comment: #0 - PRIYA M. A - 2016-06-17 10:01:28 ==
Problem Description:
- lotg5 crashed at writeback_sb_inodes+0x30c/0x590
Steps to re-create:
==
- Install lotg5 with Ubuntu16041(4.4.0-24-generic)
- Start the regression tests in lotg5
Logs:
root@lotg5:~# show.report.py
HOSTNAMEKERNEL VERSION DISTRO INFO
---
lotg5 4.4.0-24-genericUbuntu 16.04 LTS \n \l
Current Time: Fri Jun 17 01:10:46 2016
Job-ID FOCUS Start-Time DurationFunction
-- - --
1 BASE20160614-05:50:19 67.0 hr(s) 20.0 min(s) Test
2 IO 20160614-05:50:26 67.0 hr(s) 20.0 min(s) IO_Focus
3 NFS 20160614-06:24:35 66.0 hr(s) 46.0 min(s)
DistributeFS_Testing
4 TCP 20160614-06:32:03 66.0 hr(s) 38.0 min(s)
networkTest2lotg3
FOCUS BASEIO NFS TCP SUM
TOTAL 48647 1825517 82690 133679
FAIL50280 0 24 5052
PASS43619 1825517 82666 128627
(%) (89%) (100%) (100%) (99%) (96%)
DLPAR is not tested!
root@lotg5:~#
- After 65+ hr of execution lotg5 crashed with follwoing call traces
Logs:
[root@lotkvm ~]# virsh console lotg5
Connected to domain lotg5
Escape character is ^]
0:mon> c
cpus stopped: 0x0 0x4 0x8 0xc
0:mon> d
||
0:mon> e
cpu 0x0: Vector: 300 (Data Access) at [c000c4f4b620]
pc: c0323720: locked_inode_to_wb_and_lock_list+0x50/0x290
lr: c0326dbc: writeback_sb_inodes+0x30c/0x590
sp: c000c4f4b8a0
msr: 80019033
dar: 0
dsisr: 4000
current = 0xc0017191cf60
paca= 0xc7b4 softe: 0irq_happened: 0x01
pid = 5792, comm = kworker/u32:5
0:mon> t
[c000c4f4b900] c0326dbc writeback_sb_inodes+0x30c/0x590
[c000c4f4ba10] c0327124 __writeback_inodes_wb+0xe4/0x150
[c000c4f4ba70] c032758c wb_writeback+0x30c/0x450
[c000c4f4bb40] c032803c wb_workfn+0x14c/0x570
[c000c4f4bc50] c00dd1d0 process_one_work+0x1e0/0x5a0
[c000c4f4bce0] c00dd724 worker_thread+0x194/0x680
[c000c4f4bd80] c00e61e0 kthread+0x110/0x130
[c000c4f4be30] c0009538 ret_from_kernel_thread+0x5c/0xa4
--- Exception: 0 at
0:mon>
== Comment: #4 - Chandan Kumar - 2016-06-20 06:23:33 ==
dmesg log:
-
[251403.003999] EXT4-fs (loop0): mounted filesystem without journal. Opts:
(null)
[251403.471118] Unable to handle kernel paging request for data at address
0x
[251403.473391] Faulting instruction address: 0xc0323720 << PC
-
0:mon> di c0323720
c0323720 e93fld r9,0(r31)
// [R31 = , trying to de-reference null address]
c0323724 39290050addir9,r9,80
c0323728 7fbf4840cmpld cr7,r31,r9
Dominic,
Can you please take a look and assign this to suitable developer.
Thanks,
Chandan
== Comment: #6 - Laurent Dufour - 2016-06-20
13:03:15 ==
It sounds that inode->i_wb has been cleared while waiting for IO to be
dropped in writeback_sb_inodes().
That's need to be double checked...
== Comment: #10 - Laurent Dufour - 2016-06-21
05:11:35 ==
That seems to be an already known issue raised by commit 43d1c0eb7e11 "block:
detach bdev inode from its wb in __blkdev_put()".
There is a patch pushed on the lkml but there is still on going discussion
about it :
https://patchwork.kernel.org/patch/9184495/
https://lkml.org/lkml/2016/6/17/676
== Comment: #13 - Laurent Dufour - 2016-06-22
03:29:00 ==
It appears that the right way to fix that would be
https://patchwork.kernel.org/patch/9187409/.
I may build a patched ubuntu kernel on your node and you may restart the test
again.
Do you agree ?
== Comment: #14 - PRIYA M. A - 2016-06-22 03:44:00 ==
Sure Laurent. lotg5 is being installed. Will update this bug once
installation is complete so that you can apply on lotg5 and I will sta
[Kernel-packages] [Bug 1639963] Re: zfs get compressratio returns bogus results
Thanks Hajo - for some reason I didn't see your post until I'd already posted up there ^^; obviously you're correct. I don't see an obvious "close" button here, so I tagged it "invalid". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1639963 Title: zfs get compressratio returns bogus results Status in zfs-linux package in Ubuntu: Invalid Bug description: I'm running a just-installed-today copy of 16.04.1, installed from an ISO also just downloaded today from releases.ubuntu.com. root@xenial:~# lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 root@xenial:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu14 Candidate: 0.6.5.6-0ubuntu14 Version table: *** 0.6.5.6-0ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages I noticed that zfs get compressratio was not returning good results, and tested to ensure it was the compressratio reporting that was broken, not the actual compression. Demonstration: root@xenial:~# zfs get compress data/test NAME PROPERTY VALUE SOURCE data/test compression gzip local root@xenial:~# zfs list data/test NAMEUSED AVAIL REFER MOUNTPOINT data/test 2.64G 855G 2.64G /data/test Note that data/test has inline gzip compression on, and shows 2.64G of data USED. root@xenial:~# du -hs --apparent-size /data/test 9.2G /data/test root@xenial:~# du -hs /data/test 2.7G /data/test Now note that du correctly shows us that we have 9.2G of data stored in data/test (about 7G of which is actually a dump from /bin/zero for max compressibility, the other bit being an Ubuntu VM image file). We should be seeing a compressratio of about 3.41x. root@xenial:~# zfs get compressratio data/test NAME PROPERTY VALUE SOURCE data/test compressratio 1.01x - But we're seeing 1.01x. Obviously very much not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639963] Re: zfs get compressratio returns bogus results
Looks like this was an oops on my part - I got it pointed out for me that piping from /dev/zero to a filehandle results in a sparse file, which I did not understand and which explains the lack of impact from *that*. I verified that compressratio reports properly when dumping highly compressible ASCII into a dataset, so, false alarm - sorry 'bout that; closing. ** Changed in: zfs-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1639963 Title: zfs get compressratio returns bogus results Status in zfs-linux package in Ubuntu: Invalid Bug description: I'm running a just-installed-today copy of 16.04.1, installed from an ISO also just downloaded today from releases.ubuntu.com. root@xenial:~# lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 root@xenial:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu14 Candidate: 0.6.5.6-0ubuntu14 Version table: *** 0.6.5.6-0ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages I noticed that zfs get compressratio was not returning good results, and tested to ensure it was the compressratio reporting that was broken, not the actual compression. Demonstration: root@xenial:~# zfs get compress data/test NAME PROPERTY VALUE SOURCE data/test compression gzip local root@xenial:~# zfs list data/test NAMEUSED AVAIL REFER MOUNTPOINT data/test 2.64G 855G 2.64G /data/test Note that data/test has inline gzip compression on, and shows 2.64G of data USED. root@xenial:~# du -hs --apparent-size /data/test 9.2G /data/test root@xenial:~# du -hs /data/test 2.7G /data/test Now note that du correctly shows us that we have 9.2G of data stored in data/test (about 7G of which is actually a dump from /bin/zero for max compressibility, the other bit being an Ubuntu VM image file). We should be seeing a compressratio of about 3.41x. root@xenial:~# zfs get compressratio data/test NAME PROPERTY VALUE SOURCE data/test compressratio 1.01x - But we're seeing 1.01x. Obviously very much not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637666] Re: Heavy system slowdown with 4.8.0 kernel under XenServer
Sorry for the delay but I needed physical access to the host box. I upgraded XenServer to 7.0 (fully patched) and the problem persists. I tried with kernel 4.9-rc3 and the issue is still there. I reverted to 4.4.0-45 and the issue disappears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637666 Title: Heavy system slowdown with 4.8.0 kernel under XenServer Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Hello, I am experiencing a noticeable system slowdown since I upgraded from Xenial to Yakkety on several VM under XenServer 6.5 (fully patched). I understand it will be difficult for me to describe what is happening and for you to troubleshoot this issue but I'll try to do my best. Just after booting the machine is pretty responsive but after some time it starts responding very slowly. Bash autocompletion for file paths takes 1-2 seconds to respond, commands as "host" take hundred of milliseconds consuming hundred of ms of CPU. Compiling is an order of magnitude slower, etc. I wasn't able to detect what is causing the slowness. I tried to strace slow process with no evident cause. It does not seem to be something I/O bound. I ran "host" in an infinite loop causing 100% CPU usage seen from XenServer, 100% CPU usage in top but the sum of CPU usage from the processes is under 10%. top - 00:51:48 up 1 day, 4:49, 3 users, load average: 1.47, 1.02, 0.59 Tasks: 144 total, 2 running, 142 sleeping, 0 stopped, 0 zombie %Cpu(s): 74.4 us, 24.4 sy, 0.0 ni, 1.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 4044600 total, 1719740 free, 843100 used, 1481760 buff/cache KiB Swap: 2095100 total, 2095100 free,0 used. 3139664 avail Mem PID USER PR NI VIRTRESSHR S %CPU %MEM TIME+ COMMAND 30968 yggdra20 0 13460696616 R 5.8 0.0 0:00.18 host 28790 root 20 0 42020 3748 3104 R 0.6 0.1 0:02.47 top [...] I downgraded to the last Xenial kernel and the issue disappeared. I now have two VMs, with the same configuration, both yakkety, one with kernel 4.8.0-26-generic and one with 4.4.0-45-generic, on the same XenServer host. Here is what I see running host: 4.4.0-45 $ time host www.google.com www.google.com has address 216.58.198.4 www.google.com has IPv6 address 2a00:1450:4002:801::2004 real0m0.051s user0m0.032s sys 0m0.016s 4.8.0-26 --- $ time host www.google.com www.google.com has address 216.58.198.4 www.google.com has IPv6 address 2a00:1450:4002:801::2004 real0m0.412s user0m0.296s sys 0m0.096s I have other yakkety hosts on VMware and even on another XenServer 7.0 with no noticeable issues, it just seems to happen on this cluster. In the next days I will upgrade this cluster to XenServer 7.0 and I will update the bug telling if the hypervisor version is a factor. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 27 20:02 seq crw-rw 1 root audio 116, 33 Oct 27 20:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Oct 29 00:37:00 2016 HibernationDevice: RESUME=UUID=4ab77eb2-d96a-42d5-be31-b4d499646269 InstallationDate: Installed on 2011-09-19 (1866 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=0c869ff8-8fe7-41b9-89f3-9da4882b4e87 ro init=/lib/syst
Re: [Kernel-packages] [Bug 1639963] [NEW] zfs get compressratio returns bogus results
ZFS works as intended, here. Zero-filled blocks are not counted into the compression ratio, as they get dismissed early in the compression pipeline and never hit the disks as used data: # zfs create sbblht/test # dd if=/dev/zero of=/test/a bs=16M count=8 8+0 records in 8+0 records out 134217728 bytes (134 MB, 128 MiB) copied, 0.0718708 s, 1.9 GB/s root@sbooblehat:~# du -shx /test/ 1.0K/test/ root@sbooblehat:~# du -shx --apparent-size /test/ 129M/test/ # zfs list -o used,logicalused,ratio sbblht/test USED LUSED RATIO 19K 9.50K 1.00x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1639963 Title: zfs get compressratio returns bogus results Status in zfs-linux package in Ubuntu: Invalid Bug description: I'm running a just-installed-today copy of 16.04.1, installed from an ISO also just downloaded today from releases.ubuntu.com. root@xenial:~# lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 root@xenial:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu14 Candidate: 0.6.5.6-0ubuntu14 Version table: *** 0.6.5.6-0ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages I noticed that zfs get compressratio was not returning good results, and tested to ensure it was the compressratio reporting that was broken, not the actual compression. Demonstration: root@xenial:~# zfs get compress data/test NAME PROPERTY VALUE SOURCE data/test compression gzip local root@xenial:~# zfs list data/test NAMEUSED AVAIL REFER MOUNTPOINT data/test 2.64G 855G 2.64G /data/test Note that data/test has inline gzip compression on, and shows 2.64G of data USED. root@xenial:~# du -hs --apparent-size /data/test 9.2G /data/test root@xenial:~# du -hs /data/test 2.7G /data/test Now note that du correctly shows us that we have 9.2G of data stored in data/test (about 7G of which is actually a dump from /bin/zero for max compressibility, the other bit being an Ubuntu VM image file). We should be seeing a compressratio of about 3.41x. root@xenial:~# zfs get compressratio data/test NAME PROPERTY VALUE SOURCE data/test compressratio 1.01x - But we're seeing 1.01x. Obviously very much not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559469] Re: [Dell Inc. XPS 13 9350] suspend/resume failure
I have what I think is the same problem. What do I need to do to get this bug out of the expired state? (I don't understand all of how launchpad works I'm afraid.) Is this http://askubuntu.com/questions/771240/suspend-broken-on- ubuntu-16-04-lts-dell-xps-9350 the same issue? Happy to provide any extra detail needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559469 Title: [Dell Inc. XPS 13 9350] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: suspend failure, my system halt ProblemType: KernelOops 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 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1348 F pulseaudio simon 1822 F pulseaudio Date: Sat Mar 19 15:24:50 2016 DuplicateSignature: suspend/resume:Dell Inc. XPS 13 9350:1.2.3 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=975f7887-2e07-4f75-a523-7625eb0515b0 InstallationDate: Installed on 2016-03-11 (7 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-14-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: 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 Title: [Dell Inc. XPS 13 9350] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0PWNCR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0PWNCR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579542] Re: My computer reboots instead of shutdown
Bug still persist. Ive tried Ubuntu 16.04 with kernels 4.4.45 and 4.8.6. xhci_hcd.quirks=262144 and unbind xhci stop working. My computer just keeps rebooting instead of poweroff. I have to switch to Windows. This bug persist since 2013-11-29: https://bugzilla.kernel.org/show_bug.cgi?id=66171. Its a shame for Linux community but this is not my problem anymore. I was waiting 2.5 years, but you dont give a shit about your users. ** Bug watch added: Linux Kernel Bug Tracker #66171 http://bugzilla.kernel.org/show_bug.cgi?id=66171 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579542 Title: My computer reboots instead of shutdown Status in linux package in Ubuntu: Expired Bug description: Really basic operation - I go to drop-down system menu and choose "Shut down...". My computer goes poweroff but after two, maybe three seconds it starts booting process automatically. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: corsseir 1818 F pulseaudio /dev/snd/pcmC0D0p: corsseir 1818 F...m pulseaudio /dev/snd/controlC0: corsseir 1818 F pulseaudio /dev/snd/controlC1: corsseir 1818 F pulseaudio CurrentDesktop: Unity Date: Sun May 8 18:41:01 2016 InstallationDate: Installed on 2016-04-21 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=ddb69d9b-bdbe-46a8-9071-81c3762158c2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639961] libvirt.log
Default Comment by Bridge ** Attachment added: "libvirt.log" https://bugs.launchpad.net/bugs/1639961/+attachment/4774164/+files/avocado-vt-vm1.log ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639961 Title: NMI watchdog: BUG: soft lockup during KVM guest migration test suite Status in linux package in Ubuntu: New Bug description: Hello Canonical. We would like the changes in Commit 8117ac6a6c2f pulled into the Ubuntu 16.10 stream to address the following issue: == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 == ---Problem Description--- Softlock up and call trace observed from libvirtd during guest migration test suite ---uname output--- # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] message is continuous and recovered the machine with reboot 84050.059159] INFO: rcu_sched self-detected stall on CPU [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 softirq=549845/07 fqs=2176 [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484) [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] [84104.509395] INFO: rcu_sched self-detected stall on CPU [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 softirq=562249/562249 fqs=2364 [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351) [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56627] [84163.387536] INFO: rcu_sched self-detected stall on CPU [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=2354 [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297) [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56633] [84226.401597] INFO: rcu_sched self-detected stall on CPU [84226.401769]24-...: (21004 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=9697 [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145) [84289.415706] INFO: rcu_sched self-detected stall on CPU [84289.415879]24-...: (36758 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=16889 [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499) [84352.429857] INFO: rcu_sched self-detected stall on CPU [84352.430038]24-...: (52512 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=23975 [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027) [84415.444044] INFO: rcu_sched self-detected stall on CPU [84415.444222]24-...: (68266 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=31005 [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554) [84478.458262] INFO: rcu_sched self-detected stall on CPU [84478.458421]24-...: (84020 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=38023 [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030) [84541.472510] INFO: rcu_sched self-detected stall on CPU [84541.472680]24-...: (99774 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=45068 [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512) [84604.486783] INFO: rcu_sched self-detected stall on CPU Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639963] [NEW] zfs get compressratio returns bogus results
Public bug reported: I'm running a just-installed-today copy of 16.04.1, installed from an ISO also just downloaded today from releases.ubuntu.com. root@xenial:~# lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 root@xenial:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu14 Candidate: 0.6.5.6-0ubuntu14 Version table: *** 0.6.5.6-0ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages I noticed that zfs get compressratio was not returning good results, and tested to ensure it was the compressratio reporting that was broken, not the actual compression. Demonstration: root@xenial:~# zfs get compress data/test NAME PROPERTY VALUE SOURCE data/test compression gzip local root@xenial:~# zfs list data/test NAMEUSED AVAIL REFER MOUNTPOINT data/test 2.64G 855G 2.64G /data/test Note that data/test has inline gzip compression on, and shows 2.64G of data USED. root@xenial:~# du -hs --apparent-size /data/test 9.2G/data/test root@xenial:~# du -hs /data/test 2.7G/data/test Now note that du correctly shows us that we have 9.2G of data stored in data/test (about 7G of which is actually a dump from /bin/zero for max compressibility, the other bit being an Ubuntu VM image file). We should be seeing a compressratio of about 3.41x. root@xenial:~# zfs get compressratio data/test NAME PROPERTY VALUE SOURCE data/test compressratio 1.01x - But we're seeing 1.01x. Obviously very much not correct. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: zfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1639963 Title: zfs get compressratio returns bogus results Status in zfs-linux package in Ubuntu: New Bug description: I'm running a just-installed-today copy of 16.04.1, installed from an ISO also just downloaded today from releases.ubuntu.com. root@xenial:~# lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 root@xenial:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu14 Candidate: 0.6.5.6-0ubuntu14 Version table: *** 0.6.5.6-0ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages I noticed that zfs get compressratio was not returning good results, and tested to ensure it was the compressratio reporting that was broken, not the actual compression. Demonstration: root@xenial:~# zfs get compress data/test NAME PROPERTY VALUE SOURCE data/test compression gzip local root@xenial:~# zfs list data/test NAMEUSED AVAIL REFER MOUNTPOINT data/test 2.64G 855G 2.64G /data/test Note that data/test has inline gzip compression on, and shows 2.64G of data USED. root@xenial:~# du -hs --apparent-size /data/test 9.2G /data/test root@xenial:~# du -hs /data/test 2.7G /data/test Now note that du correctly shows us that we have 9.2G of data stored in data/test (about 7G of which is actually a dump from /bin/zero for max compressibility, the other bit being an Ubuntu VM image file). We should be seeing a compressratio of about 3.41x. root@xenial:~# zfs get compressratio data/test NAME PROPERTY VALUE SOURCE data/test compressratio 1.01x - But we're seeing 1.01x. Obviously very much not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1639963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639961] [NEW] NMI watchdog: BUG: soft lockup during KVM guest migration test suite
You have been subscribed to a public bug: Hello Canonical. We would like the changes in Commit 8117ac6a6c2f pulled into the Ubuntu 16.10 stream to address the following issue: == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 == ---Problem Description--- Softlock up and call trace observed from libvirtd during guest migration test suite ---uname output--- # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] message is continuous and recovered the machine with reboot 84050.059159] INFO: rcu_sched self-detected stall on CPU [84050.059339] 24-...: (5659 ticks this GP) idle=fa5/141/0 softirq=549845/07 fqs=2176 [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484) [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800] [84104.509395] INFO: rcu_sched self-detected stall on CPU [84104.509591] 24-...: (5659 ticks this GP) idle=5df/141/0 softirq=562249/562249 fqs=2364 [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351) [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56627] [84163.387536] INFO: rcu_sched self-detected stall on CPU [84163.387716] 24-...: (5250 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=2354 [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297) [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [virsh:56633] [84226.401597] INFO: rcu_sched self-detected stall on CPU [84226.401769] 24-...: (21004 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=9697 [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145) [84289.415706] INFO: rcu_sched self-detected stall on CPU [84289.415879] 24-...: (36758 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=16889 [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499) [84352.429857] INFO: rcu_sched self-detected stall on CPU [84352.430038] 24-...: (52512 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=23975 [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027) [84415.444044] INFO: rcu_sched self-detected stall on CPU [84415.444222] 24-...: (68266 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=31005 [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554) [84478.458262] INFO: rcu_sched self-detected stall on CPU [84478.458421] 24-...: (84020 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=38023 [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030) [84541.472510] INFO: rcu_sched self-detected stall on CPU [84541.472680] 24-...: (99774 ticks this GP) idle=f69/142/0 softirq=562274/562274 fqs=45068 [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512) [84604.486783] INFO: rcu_sched self-detected stall on CPU Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-146681 severity-high targetmilestone-inin--- -- NMI watchdog: BUG: soft lockup during KVM guest migration test suite https://bugs.launchpad.net/bugs/1639961 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 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot
Another workaround that worked for me is to edit /etc/default/grub like so: GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" followed by update-grub2 I am running with full disk encryption. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638990 Title: nvidia-367 with kernel 4.4.0-45-generic won't boot Status in linux package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy linux-image-4.4.0.45-generic linux-image-4.4.0-45-generic: Installed: 4.4.0-45.66 Candidate: 4.4.0-45.66 Version table: *** 4.4.0-45.66 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status After hitting bug 1633172 and the workaround putting me in a worse state than the initial bug, I started from scratch with Xenial. That worked for a short 24 hours. Then this morning, I got an update for my nvidia drivers. After I upgraded the drivers, I could no longer boot into ubuntu with kernel 4.4.0-45-generic. If I booted with kernel 4.4.0-31-generic, I no longer had an issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lost 2248 F pulseaudio /dev/snd/controlC0: lost 2248 F pulseaudio /dev/snd/controlC1: lost 2248 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 3 12:12:55 2016 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638278] Re: 4.8 kernel, under heavy load desktop unusable
@jsalisbury - I tried your kernel, it fixes the issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638278 Title: 4.8 kernel, under heavy load desktop unusable Status in linux package in Ubuntu: Confirmed Bug description: I've updated from Xenial to Yakkety on my Desktop - Sandybridge Macbook Pro 8,1 With Xenial, on 4.4 kernel, doing a compile (with ninja for example), I could use all CPU cores and still have a usable desktop: app switching was relatively quick, I could (slowly) surf the web while the compile was happening. Now with Yakkety 4.8 kernel, doing a compile using all cores totally seizes up my desktop - app switching is incredibly slow, I see redraw errors, mouse has poor response. As a workaround, I have to manually leave a CPU core free when compiling. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gerry 4929 F...m pulseaudio /dev/snd/controlC0: gerry 4929 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 1 12:02:02 2016 HibernationDevice: RESUME=UUID=2cba34fc-e62e-44c2-904a-1f3f96fbc5eb InstallationDate: Installed on 2016-05-05 (179 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookPro8,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed root=UUID=a9e3a76e-0502-4f4e-a8d9-132fb83f44b1 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2016-10-27 (4 days ago) dmi.bios.date: 10/26/15 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B2C.1510261540 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2C.1510261540:bd10/26/15:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81: dmi.product.name: MacBookPro8,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. klp-taint: 12289 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1631892] Re: Broadcom b43 Wifi no longer working in 16.04
Ok. After a few days of usage & quite a many boot sequences, I can confirm that this wifi issue with b43 driver is not solved with the 4.8.6 kernel.. 4/5 times upon booting I have to unload & reload b43 (usually twice before it kicks in) :( Anything else I can do/provide to help troubleshoot the source of this regression? 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/1631892 Title: Broadcom b43 Wifi no longer working in 16.04 Status in linux package in Ubuntu: Incomplete Bug description: I've installed the new 16.04.1 (elementaryOS Loki) - removed `wl` wifi driver [which for some reason was installed even though I did NOT choose the option to install non-free software (mp3, etc..)]. I then connected via ethernet, installed b43 via its `firmware- installer` package. My wifi sometimes works, ie. if manages to join a network, then all is cool, no disconnects, no problem. But many many times though, I can't join a wifi network.. :( Let me know any further info, test, and/or troubleshooting I can do to help figure out where this regression is coming from. I say regression because I was using 14.04.5 (elementaryOS Freya) and used b43 as wifi driver - and never had problems with wifi networks, it just worked fine. ProblemType: Bug DistroRelease: elementary 0.4 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 [modified: boot/vmlinuz-4.4.0-38-generic] [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben1764 F pulseaudio CurrentDesktop: Pantheon Date: Sat Oct 8 11:57:22 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=cb3f9d25-a669-4e37-88a8-5d2849db0489 InstallationDate: Installed on 2016-10-01 (6 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) MachineType: Apple Inc. MacBookPro7,1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/elementary--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0E.071400 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0E.071400:bd11/07/11:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627217] Re: ipv6 forwarding kernel oops
Anything new with this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627217 Title: ipv6 forwarding kernel oops Status in linux package in Ubuntu: Confirmed Bug description: After a box is configured as an ipv6 router and net.ipv6.conf.enp1s0.accept_ra=2 is set the kernel panics when it tries to forward packets. The crash occurs after a few packets go through. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/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: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Fri Sep 23 17:21:03 2016 HibernationDevice: RESUME=/dev/mapper/wormhole--vg-swap_1 InstallationDate: Installed on 2016-09-21 (2 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: MSI MS-7599 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 XGI ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux StagingDrivers: xgifb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 870-G45 (MS-7599) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd08/30/2013:svnMSI:pnMS-7599:pvr2.0:rvnMSI:rn870-G45(MS-7599):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7599 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Fix Released ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636941 Title: linux: 4.4.0-47.68 -proposed tracker Status in Kernel SRU Workflow: Incomplete Status in Kernel SRU Workflow automated-testing series: New 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-47.68 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1636941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
thanks, I'm still determined to try a few more things. If nothing works, I have no choice but to try i8kutils anyway. And I feel better having a reference config that works from someone with the same machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635242] Re: linux: 4.4.0-46.67 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635242 Title: linux: 4.4.0-46.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-46.67 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635377] Re: linux: 4.8.0-27.29 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635377 Title: linux: 4.8.0-27.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-27.29 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635430] Re: linux: 3.13.0-101.148 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Invalid => Fix Released ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635430 Title: linux: 3.13.0-101.148 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-101.148 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635437] Re: linux-lts-trusty: 3.13.0-101.148~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1635437 Title: linux-lts-trusty: 3.13.0-101.148~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the 3.13.0-101.148~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1635430 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
Test build with CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=1 is done. http://people.canonical.com/~sforshee/lp1636847/linux-4.4.0-46.67+lp1636847v201611071220/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1629977] Re: sha1-powerpc returning wrong results
** Tags removed: verification-needed-trusty verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-trusty verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1629977 Title: sha1-powerpc returning wrong results Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: The driver sha1-powerpc fails all tests in the crypto API test manager. The driver was not written with little endian support. The simplest steps to check the problem is to recompile the kernel with the crypto API test manager enabled (since it's disabled by default on Xenial) and then load the sha1-powerpc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630970] Re: crypto/vmx/p8_ghash memory corruption
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630970 Title: crypto/vmx/p8_ghash memory corruption Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: That bug was reported on the linux-crypto mailing list by Jan Stancek. The bug is not easily reproduced on Xenial because the crypto API test manager is not enabled and the hash test that exorcises this bug is not present on the Xenial kernel. --- Hi, I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers an Oops, for example: [ 88.486041] Unable to handle kernel paging request for data at address 0x0020 ... [ 88.487658] NIP [c020f820] m_show+0xa0/0x240 [ 88.487689] LR [c020f834] m_show+0xb4/0x240 [ 88.487719] Call Trace: [ 88.487736] [c004b605bbb0] [c020f834] m_show+0xb4/0x240 (unreliable) [ 88.487796] [c004b605bc50] [c045e73c] seq_read+0x36c/0x520 [ 88.487843] [c004b605bcf0] [c04e1014] proc_reg_read+0x84/0x120 [ 88.487889] [c004b605bd30] [c040df88] vfs_read+0xf8/0x380 [ 88.487934] [c004b605bde0] [c040fd40] SyS_read+0x60/0x110 [ 88.487981] [c004b605be30] [c0009590] system_call+0x38/0xec 0x20 offset is module_use->source, module_use is NULL because module.source_list gets corrupted. The source of corruption appears to originate from a 'ahash' test for p8_ghash: cryptomgr_test alg_test alg_test_hash test_hash __test_hash ahash_partial_update shash_async_export memcpy With some extra traces [1], I'm seeing that ahash_partial_update() allocates 56 bytes for 'state', and then crypto_ahash_export() writes 76 bytes into it: [5.970887] __test_hash alg name p8_ghash, result: c4333ac0, key: c004b860a500, req: c004b860a380 [5.970963] state: c4333f00, statesize: 56 [5.970995] shash_default_export memcpy c4333f00 c004b860a3e0, len: 76 This seems to directly correspond with: p8_ghash_alg.descsize = sizeof(struct p8_ghash_desc_ctx) == 56 shash_tfm->descsize = sizeof(struct p8_ghash_desc_ctx) + crypto_shash_descsize(fallback) == 56 + 20 where 20 is presumably coming from "ghash_alg.descsize". My gut feeling was that these 2 should match, but I'd love to hear what crypto people think. Thank you, Jan --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
note: that for xenial there are several pieces that must land as different SRUs. Just using the xenial SRU kernel is not sufficient. There is an apparmor userspace SRU that is required, and squashfuse sru ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
Based on feedback from @jjohansen there will be follow-up patches to fix the problems, but the patches already applied should be kept and do not need to be reverted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1613134] Re: wacom touch screen does not recognize finger touch
@penalvch: Since yakkety runs on the 4.8 kernel this issue is fixed, and so it is with the daily build. I'm looking forward to a backport/fix for the LTS. @ET: I've done the kernel bisection on a fresh installation, so there is no difference between an old and a fresh installation. By the way, I never needed an inputattach command since the first installation of 12.04. Seems to be a different touch device and thus a different issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613134 Title: wacom touch screen does not recognize finger touch Status in linux package in Ubuntu: Incomplete Bug description: After Updating to Xenail, the touch screen does not recognize finger touch as input, stylus and eraser are still recognized. This bug affects the Wacom Serial Penabled 2FG Touchscreen, which is built into the HP EliteBook 2760p and the Lenovo Thinkpad X201. It is already reported for other linux distributions. See bugreports: archlinux: https://bbs.archlinux.org/viewtopic.php?id=215014 linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=120011 xsetwacom lists the devices: Wacom Serial Penabled 2FG Touchscreen Pen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen Finger touchid: 14 type: TOUCH Wacom Serial Penabled 2FG Touchscreen Pen eraser id: 16 type: ERASER a downgrade to Package: linux-image-4.2.0-42-generic 4.2.0-42.49 (from wily) brings back the finger touch. xsetwacom lists the available devices slightly different: littlelion@PC00-C846:~$ xsetwacom list devices Wacom Serial Penabled 2FG Touchscreen stylus id: 13 type: STYLUS Wacom Serial Penabled 2FG Touchscreen eraser id: 15 type: ERASER Wacom Serial Penabled 2FG Touchscreen touch id: 16 type: TOUCH ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: littlelion 4149 F pulseaudio CurrentDesktop: Unity Date: Mon Aug 15 02:32:09 2016 HibernationDevice: RESUME=UUID=46ec6e40-eed3-4377-b3e1-4eed675fba2e InstallationDate: Installed on 2012-10-16 (1398 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Hewlett-Packard HP EliteBook 2760p ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=81ff9b66-4d33-49d5-a76f-cf1418c3e354 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-06 (8 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SOU Ver. F.50 dmi.board.name: 162A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 05.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SOUVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2760p dmi.product.version: A0005F02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
https://lists.ubuntu.com/archives/kernel-team/2016-November/080739.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/1304001 Title: xen:balloon errors in 14.04 beta Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639560] Re: linux-image-4.8.0-26-generic causes complete system freeze
FWIW, reverting to the previous kernel linux-image-4.8.0-22-generic fixes another graphic bug I experienced with LibreOffice on Kubuntu: https://bugs.documentfoundation.org/show_bug.cgi?id=103676 ** Bug watch added: Document Foundation Bugzilla #103676 https://bugs.documentfoundation.org/show_bug.cgi?id=103676 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639560 Title: linux-image-4.8.0-26-generic causes complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: Hello, When using kernel linux-image-4.8.0-26-generic 4.8.0-26.28 and after applying latest available updates, the system randomly freezes/hangs and a forced shutdown is required. It can be easily reproduced by trying to press the "logout" button. The system would immediately hang. Reverting to previous kernel, 4.8.0-22.24 fixes the issue. My hardware is a Dell XPS 13 laptop, model 9343. It has the Intel HD graphics card, using i915 module. Description: Ubuntu 16.10 Release: 16.10 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639810] Re: igb i210 probe of pci device failed with error -2
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639810 Title: igb i210 probe of pci device failed with error -2 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: [Impact] Intel I210 NIC may show: 'igb: probe of :07:00.0 failed with error -2' Upon boot after power has been completely disconnected. I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. This also happens with the linux 4.9-rc4. [Fix] https://patchwork.ozlabs.org/patch/690464/ This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue. [Test Case] Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639810] Re: igb i210 probe of pci device failed with error -2
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Tags added: chris-arges ** Tags added: is-back ** Tags added: yay -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639810 Title: igb i210 probe of pci device failed with error -2 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: [Impact] Intel I210 NIC may show: 'igb: probe of :07:00.0 failed with error -2' Upon boot after power has been completely disconnected. I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. This also happens with the linux 4.9-rc4. [Fix] https://patchwork.ozlabs.org/patch/690464/ This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue. [Test Case] Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
Colin, thank you for the fix, I will switch to xenial-proposed now.
As a followup, upstream merged my PR so 1014-kernel-lookup-bdev.patch
may be removed once the next ZFS on Linux release gets synced to us,
hopefully in time for zesty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in zfs-linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
New
Status in zfs-linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Triaged
Status in zfs-linux source package in Zesty:
Fix Released
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
zfsutils-linux:
Zesty: https://launchpadlibrarian.net/290907232/zfs-
linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
Sync'd fixes into kernel repos, patches in:
http://kernel.ubuntu.com/~cking/zfs-lp-1636517
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.7
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-p
[Kernel-packages] [Bug 1637437] Re: linux 3.13.0-101.148 ADT test failure with linux 3.13.0-101.148
This appears to be a problem with the test ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637437 Title: linux 3.13.0-101.148 ADT test failure with linux 3.13.0-101.148 Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux/20161024_111739_42e49@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1637437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637440] Re: linux 4.4.0-46.67 ADT test failure with linux 4.4.0-46.67
This appears to be an issue with the test. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637440 Title: linux 4.4.0-46.67 ADT test failure with linux 4.4.0-46.67 Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20161027_080747_183c5@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1637440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639560] Re: linux-image-4.8.0-26-generic causes complete system freeze
I have the same problem: with kernel linux-image-4.8.0-26-generic, the system randomly freezes completely (black screen, no network) a few time a day with no apparent correlation to any software activity or cpu heat. My laptop is an HP ProBook 6550b. GPU: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) Driver: i915 Kubuntu 16.10 recently upgraded. The only difference with OP is that it doesn't freeze when I logout. I just reverted to linux-image-4.8.0-22-generic. I'll post here whether it fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639560 Title: linux-image-4.8.0-26-generic causes complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: Hello, When using kernel linux-image-4.8.0-26-generic 4.8.0-26.28 and after applying latest available updates, the system randomly freezes/hangs and a forced shutdown is required. It can be easily reproduced by trying to press the "logout" button. The system would immediately hang. Reverting to previous kernel, 4.8.0-22.24 fixes the issue. My hardware is a Dell XPS 13 laptop, model 9343. It has the Intel HD graphics card, using i915 module. Description: Ubuntu 16.10 Release: 16.10 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628976] Re: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng.
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628976 Title: Ubuntu 16.10: Oops panic in move_page_tables/page_remove_rmap after running memory_stress_ng. Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: FYI Canonical: We have been seeing various page handling issues during memory stress in the 4.8 kernels. The following is the most recent issue resulting in system panics on this host after the 4.8.0-17 update: == Comment: #17 - PAVITHRA R. PRAKASH - 2016-09-28 06:26:21 == Hi, Tried running on 4.8.0-17-generic kernel. Getting below call trace and system crashes. Attaching logs. [ 2959.364333] Unable to handle kernel paging request for data at address 0xf2fe4020 [ 2959.364345] Faulting instruction address: 0xc02bb2a0 [ 2959.364356] Oops: Kernel access of bad area, sig: 11 [#1] [ 2959.364364] SMP NR_CPUS=2048 NUMA pSeries [ 2959.364377] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag bnx2x mdio libcrc32c pseries_rng vmx_crypto binfmt_misc ip_tables x_tables autofs4 ibmvscsi crc32c_vpmsum [ 2959.364441] CPU: 13 PID: 108 Comm: oom_reaper Not tainted 4.8.0-17-generic #19-Ubuntu [ 2959.364452] task: c004fbdf9c00 task.stack: c004fbe0 [ 2959.364461] NIP: c02bb2a0 LR: c0300618 CTR: c009ca40 [ 2959.364471] REGS: c004fbe036e0 TRAP: 0300 Not tainted (4.8.0-17-generic) [ 2959.364481] MSR: 80010280b033 CR: 24028844 XER: 200c [ 2959.364526] CFAR: c0300614 DAR: f2fe4020 DSISR: 4000 SOFTE: 1 GPR00: c0300618 c004fbe03960 c14e5e00 f2fe4000 GPR04: 0001 0800 c1665e00 GPR08: f900a196 0001 02fe4000 GPR12: 8800 c1b37500 0008 c1ffe7ff GPR16: c004f62a55f0 3fff9a00 3fff9900 GPR20: c004fbe03b80 c004e0713800 8e017c3302c0 0001 GPR24: c000fb3614c8 c000fce9d990 c000fce9d6e4 96a100f90b40 GPR28: f2fe4000 c000fb3614c8 0001 f2fe4000 [ 2959.364673] NIP [c02bb2a0] page_remove_rmap+0x30/0x4b0 [ 2959.364685] LR [c0300618] zap_huge_pmd+0xf8/0x480 [ 2959.364692] Call Trace: [ 2959.364699] [c004fbe03960] [c004fbe039a0] 0xc004fbe039a0 (unreliable) [ 2959.364714] [c004fbe039a0] [c0300618] zap_huge_pmd+0xf8/0x480 [ 2959.364726] [c004fbe039f0] [c02a68d8] unmap_page_range+0xd08/0xee0 [ 2959.364740] [c004fbe03b20] [c025c474] __oom_reap_task+0x204/0x2c0 [ 2959.364752] [c004fbe03c80] [c025cda8] oom_reaper+0x1e8/0x300 [ 2959.364765] [c004fbe03d80] [c00fd120] kthread+0x110/0x130 [ 2959.364778] [c004fbe03e30] [c00098f0] ret_from_kernel_thread+0x5c/0x6c [ 2959.364788] Instruction dump: [ 2959.364796] 3c4c0123 3842ab90 7c0802a6 fba1ffe8 fbc1fff0 fbe1fff8 f8010010 f821ffc1 [ 2959.364821] 7c7f1b78 7c9e2378 6000 6000 71480001 392a 40820008 [ 2959.364871] ---[ end trace 178b14c6911b70dc ]--- [ 2959.372762] [ 2959.372798] Sending IPI to other CPUs [ 2959.373834] IPI complete Thanks, Pavithra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
This is what I am using, but I am not taking any responsibility of
damage caused on your laptop. :) Also you can play with the temps to get
the fan speeds to you satisfaction...
# /etc/i8kmon.conf
# Run as daemon, override with --daemon option
set config(daemon) 0
# Automatic fan control, override with --auto option
set config(auto)1
# Report status on stdout, override with --verbose option
set config(verbose) 1
# Status check timeout (seconds), override with --timeout option
set config(timeout) 20
# For computer with 2 fans, use a variant of this instead:
# Temperature thresholds: {fan_speeds low_ac high_ac low_batt high_batt}
set config(0) {{0 0} -1 55 -1 55}
set config(1) {{1 1} 36 65 36 65}
set config(2) {{1 1} 50 75 50 75}
set config(3) {{2 2} 70 128 70 128}
# end of file
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1602888
Title:
Dell Inspiron 7559 fans do not shut off once started, even when cool
Status in linux package in Ubuntu:
Triaged
Bug description:
Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
be an issue with the fan control. When I first boot up the machine the
fans are off. However, after the laptop warms up under normal usage,
the fans kick on and then never shut off again. Even when the CPU
cools down to below 35c, the fans will continue to run.
If I suspend the the laptop, and then immediately wake it up again
then fans are once again off, until it warms up again. So
essentially, once the fans start they don't seem to ever shut off.
Fans seem to work normally under Windows 10. They turn on as needed,
and then turn off once the laptop cools down.
I've tried the various BIOS updates that Dell has released, without
success. I am currently running Dell's latest BIOS for this laptop
(v1.1.8)
Below is the output of lm-sensors showing the fans running when the
CPU is at a cool 35c
dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 1925 RPM
Processor Fan: 2143 RPM
CPU:+35.0°C
GPU: +1.0°C
SODIMM: +49.0°C
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob1709 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 13 19:18:45 2016
HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
InstallationDate: Installed on 2016-07-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 7559
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
@zyga: I'm honestly very surprised that the config change had that drastic an impact on the single-CPU system. Can you tell me what 'cat /sys/devices/system/cpu/possible' says on that system? Can I assume that the "size-1M" implies a 1MB block size? Let's start with the simplest options for reducing RAM usage. The most obvious place for gains is the buffers squashfs uses for decompression and caching. squashfs has three caches: - The "metadata" cache caches 8 blocks of metadata. The metadata block size is fixed at 8KB and the cache is fixed at 8 blocks, so this consumes 64KB of RAM (plus overhead). So there isn't a lot to be gained here. - The "data" cache is the one affected by CONFIG_SQUASHFS_DECOMP_SINGLE. squashfs allocates RAM up front for each possible decompression thread, at fs_block_size bytes per thread. The previously used config option allocated one cache per possible system in the CPU (which is why I was suprised at the numbers for the single CPU system; at a 1MB block size that implies the system supports over 100 CPUs). The only simple way to gain more here would be to reduce the block size of the filesystems. - The "fragment" cache. This caches CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE blocks, which is currently set to 3 in our kernels. So it would seem that this accounts for the bulk of the remaining RAM usage. That means for a 1MB block size it's a fixed size of 3MB. We could reduce this to 1 to save some RAM, and reducing the block size of the squashfs images would again help here. So if the images do have a 1MB block size there are two simple things that will yield the biggest gains - reducing the fragment cache to 1 block and reducing the block size of the squashfs images. Obviously any reduction in cache sizes may result in a loss of performance, depending on access patterns. I'll go ahead and build a kernel with CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=1 for you to test. I would suggest taking a look at performance in addition to RAM usage when you're testing. If 1MB is the block size you're using, would you be open to making this smaller? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot
FYI, nvidia-367 works with kernel 4.4.0-43-generic. Might be an acceptable workaround for some people until this bug is fixed. Rebuilding nvidia-367 using dpkg-reconfigure under kernel 4.4.0-45 didn't work for me. Neither did reinstalling it (probably not much of a different effect). Also wanted to mention that the initial symptom of this problem in the presence of full-disk encryption is that the boot fails very early, before it even asks for your FDE passphrase. It surprised me to find that the nvidia driver or some part of it is loaded that early. I thought by HDD had failed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638990 Title: nvidia-367 with kernel 4.4.0-45-generic won't boot Status in linux package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ~$ apt-cache policy linux-image-4.4.0.45-generic linux-image-4.4.0-45-generic: Installed: 4.4.0-45.66 Candidate: 4.4.0-45.66 Version table: *** 4.4.0-45.66 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status After hitting bug 1633172 and the workaround putting me in a worse state than the initial bug, I started from scratch with Xenial. That worked for a short 24 hours. Then this morning, I got an update for my nvidia drivers. After I upgraded the drivers, I could no longer boot into ubuntu with kernel 4.4.0-45-generic. If I booted with kernel 4.4.0-31-generic, I no longer had an issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lost 2248 F pulseaudio /dev/snd/controlC0: lost 2248 F pulseaudio /dev/snd/controlC1: lost 2248 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 3 12:12:55 2016 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
This bug still exists in Precise with 3.2.0-113. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: --> pirq=16 -> irq=8 (gsi=8) [0.562622] xen: --> pirq=17 -> irq=12 (gsi=12) [0.562649] xen: --> pirq=18 -> irq=1 (gsi=1) [0.562673] xen: --> pirq=19 -> irq=6 (gsi=6) [0.562705] xen: --> pirq=20 -> irq=4 (gsi=4) [0.920527] xen: --> pirq=21 -> irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634129] Re: Couldn't emulate instruction 0x7813427c
p...@au1.ibm.com - what are the 2 commits ? I can only see commit
fa73c3b25bd8 ("KVM: PPC: Book3s PR: Allow access to unprivileged MMCR2
register", 2016-09-21) mentioned.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1634129
Title:
Couldn't emulate instruction 0x7813427c
Status in linux package in Ubuntu:
New
Bug description:
Couldn't emulate instruction 0x7813427c
---
Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel.
It worked until Vivid (in spite of not being possible in x86)
TCG mode works fine, but very slow.
TCG full emulation is the mode in the x86 world for nested virt.
However, in Power, we've been using in OpenStack CI w/ kvm accel
(native virtualization) to speed up 2nd level VMs. It worked until
Vivid.
Is the case that kvm accel isn't possible anymore for nested virt
(aligned with x86 KVM) ? So full emulation TCG mode is the only
possible mode in newer kernels ?
qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable-
kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le-
disk.img
lsmod |grep kvm
kvm_pr 96452 1
kvm 152984 4 kvm_pr
Nested VM console:
OF stdout device is: /vdevice/vty@7100
Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018)
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri
Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13)
Detected machine type: 0101
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro
memory layout at init:
memory_limit : (16 MB aligned)
alloc_bottom : 0421
alloc_top: 1000
alloc_top_hi : 4000
rmo_top : 1000
ram_top : 4000
found display : /pci@8002000/vga@0, opening... done
instantiating rtas at 0x0daf... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0422 -> 0x04220aa9
Device tree struct 0x0423 -> 0x0424
Quiescing Open Firmware ...
Booting Linux via __start() ?
/var/log/syslog & /var/log/kern.log
Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975]
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate
instruction 0x7813427c (op 30 xop 318)
Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066]
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate
instruction 0x7813427c (op 30 xop 318)
Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156]
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
Host:
cpu : POWER8E (raw), altivec supported
clock : 3690.00MHz
revision : 2.1 (pvr 004b 0201)
timebase : 51200
platform : PowerNV
model : 8247-22L
machine : PowerNV 8247-22L
firmware : OPAL v3
Guest: Xenial or Yakkety
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
Nested VM:
CirrOS
http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img
This seems to be related
https://patchwork.kernel.org/patch/9121881/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634129/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639506] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1639506 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/1639506 Title: panic in i915 Status in linux package in Ubuntu: Incomplete Bug description: Linux myhost 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC 2016 i686 i686 i686 GNU/Linux syslog: Nov 5 21:15:45 myhost kernel: [ 53.532149] [ cut here ] Nov 5 21:15:45 myhost kernel: [ 53.532252] WARNING: CPU: 0 PID: 369 at /build/linux-LfgES4/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12744 intel_modeset_check_state+0x556/0x910 [i915]() Nov 5 21:15:45 myhost kernel: [ 53.532257] encoder's enabled state mismatch (expected 0, found 1) Nov 5 21:15:45 myhost kernel: [ 53.532261] Modules linked in: xt_tcpudp xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel ppdev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi ax88179_178a lpc_ich serio_raw snd_seq usbnet snd_seq_device snd_timer snd shpchp soundcore parport_pc 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 ahci psmouse r8169 libahci i2c_algo_bit drm_kms_helper pata_acpi syscopyarea sysfillrect sysimgblt fb_sys_fops drm mii fjes video Nov 5 21:15:45 myhost kernel: [ 53.532402] CPU: 0 PID: 369 Comm: kworker/0:2 Tainted: GW 4.4.0-45-generic #66-Ubuntu Nov 5 21:15:45 myhost kernel: [ 53.532406] Hardware name: /D945GSEJT , BIOS JT94510H.86A.0025.2009.0306.1639 03/06/2009 Nov 5 21:15:45 myhost kernel: [ 53.532432] Workqueue: events output_poll_execute [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.532438] c1acf967 c1e2b340 0286 f15d1d20 c13a745f f15d1d60 f89d68b8 f15d1d50 Nov 5 21:15:45 myhost kernel: [ 53.532451] c1070307 f89d89c8 f15d1d80 0171 f89d68b8 31c8 f896b696 f896b696 Nov 5 21:15:45 myhost kernel: [ 53.532463] f58bc5d8 f5b6ea80 f58bc5e4 f15d1d6c c107037e 0009 f15d1d60 f89d89c8 Nov 5 21:15:45 myhost kernel: [ 53.532475] Call Trace: Nov 5 21:15:45 myhost kernel: [ 53.532488] [] dump_stack+0x58/0x79 Nov 5 21:15:45 myhost kernel: [ 53.532498] [] warn_slowpath_common+0x87/0xc0 Nov 5 21:15:45 myhost kernel: [ 53.532585] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532667] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532674] [] warn_slowpath_fmt+0x3e/0x60 Nov 5 21:15:45 myhost kernel: [ 53.532757] [] intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532841] [] intel_atomic_commit+0x4cd/0x6a0 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532894] [] ? drm_atomic_check_only+0x1ae/0x600 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532943] [] ? drm_modeset_lock+0x49/0xd0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532994] [] drm_atomic_commit+0x32/0x60 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533020] [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533070] [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533096] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533121] [] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533146] [] drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533229] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] Nov 5 21:15:45 myhost kernel: [ 53.533252] [] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533276] [] output_poll_execute+0x188/0x1c0 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533285] [] process_one_work+0x121/0x3f0 Nov 5 21:15:45 myhost kernel: [ 53.533292] [] worker_thread+0x20a/0x490 Nov 5 21:15:45 myhost kernel: [ 53.533300] [] ? proc
[Kernel-packages] [Bug 1639506] Re: panic in i915
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639506 Title: panic in i915 Status in linux package in Ubuntu: Incomplete Bug description: Linux myhost 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC 2016 i686 i686 i686 GNU/Linux syslog: Nov 5 21:15:45 myhost kernel: [ 53.532149] [ cut here ] Nov 5 21:15:45 myhost kernel: [ 53.532252] WARNING: CPU: 0 PID: 369 at /build/linux-LfgES4/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12744 intel_modeset_check_state+0x556/0x910 [i915]() Nov 5 21:15:45 myhost kernel: [ 53.532257] encoder's enabled state mismatch (expected 0, found 1) Nov 5 21:15:45 myhost kernel: [ 53.532261] Modules linked in: xt_tcpudp xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel ppdev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi ax88179_178a lpc_ich serio_raw snd_seq usbnet snd_seq_device snd_timer snd shpchp soundcore parport_pc 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 ahci psmouse r8169 libahci i2c_algo_bit drm_kms_helper pata_acpi syscopyarea sysfillrect sysimgblt fb_sys_fops drm mii fjes video Nov 5 21:15:45 myhost kernel: [ 53.532402] CPU: 0 PID: 369 Comm: kworker/0:2 Tainted: GW 4.4.0-45-generic #66-Ubuntu Nov 5 21:15:45 myhost kernel: [ 53.532406] Hardware name: /D945GSEJT , BIOS JT94510H.86A.0025.2009.0306.1639 03/06/2009 Nov 5 21:15:45 myhost kernel: [ 53.532432] Workqueue: events output_poll_execute [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.532438] c1acf967 c1e2b340 0286 f15d1d20 c13a745f f15d1d60 f89d68b8 f15d1d50 Nov 5 21:15:45 myhost kernel: [ 53.532451] c1070307 f89d89c8 f15d1d80 0171 f89d68b8 31c8 f896b696 f896b696 Nov 5 21:15:45 myhost kernel: [ 53.532463] f58bc5d8 f5b6ea80 f58bc5e4 f15d1d6c c107037e 0009 f15d1d60 f89d89c8 Nov 5 21:15:45 myhost kernel: [ 53.532475] Call Trace: Nov 5 21:15:45 myhost kernel: [ 53.532488] [] dump_stack+0x58/0x79 Nov 5 21:15:45 myhost kernel: [ 53.532498] [] warn_slowpath_common+0x87/0xc0 Nov 5 21:15:45 myhost kernel: [ 53.532585] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532667] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532674] [] warn_slowpath_fmt+0x3e/0x60 Nov 5 21:15:45 myhost kernel: [ 53.532757] [] intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532841] [] intel_atomic_commit+0x4cd/0x6a0 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532894] [] ? drm_atomic_check_only+0x1ae/0x600 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532943] [] ? drm_modeset_lock+0x49/0xd0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532994] [] drm_atomic_commit+0x32/0x60 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533020] [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533070] [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533096] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533121] [] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533146] [] drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533229] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] Nov 5 21:15:45 myhost kernel: [ 53.533252] [] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533276] [] output_poll_execute+0x188/0x1c0 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533285] [] process_one_work+0x121/0x3f0 Nov 5 21:15:45 myhost kernel: [ 53.533292] [] worker_thread+0x20a/0x490 Nov 5 21:15:45 myhost kernel: [ 53.533300] [] ? process_one_work+0x3f0/0x3f0 Nov 5 21:15:45 myhost kernel: [ 53.533306] [] kthread+0xa6/0xc0 Nov 5 21:15:45 myhost kernel: [ 53.533315] [] ret_from_kernel_thread+0x21/0x38 Nov 5 21:15:45 myhost kernel: [ 53.533321] [] ? kthread_create_on_node+0x170/0x170 Nov 5 21:15:45 myhost kernel: [ 53.533327] ---[ end trace 361aeae89ccf24ea ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639506/+sub
[Kernel-packages] [Bug 1639506] [NEW] panic in i915
You have been subscribed to a public bug: Linux myhost 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC 2016 i686 i686 i686 GNU/Linux syslog: Nov 5 21:15:45 myhost kernel: [ 53.532149] [ cut here ] Nov 5 21:15:45 myhost kernel: [ 53.532252] WARNING: CPU: 0 PID: 369 at /build/linux-LfgES4/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12744 intel_modeset_check_state+0x556/0x910 [i915]() Nov 5 21:15:45 myhost kernel: [ 53.532257] encoder's enabled state mismatch (expected 0, found 1) Nov 5 21:15:45 myhost kernel: [ 53.532261] Modules linked in: xt_tcpudp xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel ppdev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi ax88179_178a lpc_ich serio_raw snd_seq usbnet snd_seq_device snd_timer snd shpchp soundcore parport_pc 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 ahci psmouse r8169 libahci i2c_algo_bit drm_kms_helper pata_acpi syscopyarea sysfillrect sysimgblt fb_sys_fops drm mii fjes video Nov 5 21:15:45 myhost kernel: [ 53.532402] CPU: 0 PID: 369 Comm: kworker/0:2 Tainted: GW 4.4.0-45-generic #66-Ubuntu Nov 5 21:15:45 myhost kernel: [ 53.532406] Hardware name: /D945GSEJT , BIOS JT94510H.86A.0025.2009.0306.1639 03/06/2009 Nov 5 21:15:45 myhost kernel: [ 53.532432] Workqueue: events output_poll_execute [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.532438] c1acf967 c1e2b340 0286 f15d1d20 c13a745f f15d1d60 f89d68b8 f15d1d50 Nov 5 21:15:45 myhost kernel: [ 53.532451] c1070307 f89d89c8 f15d1d80 0171 f89d68b8 31c8 f896b696 f896b696 Nov 5 21:15:45 myhost kernel: [ 53.532463] f58bc5d8 f5b6ea80 f58bc5e4 f15d1d6c c107037e 0009 f15d1d60 f89d89c8 Nov 5 21:15:45 myhost kernel: [ 53.532475] Call Trace: Nov 5 21:15:45 myhost kernel: [ 53.532488] [] dump_stack+0x58/0x79 Nov 5 21:15:45 myhost kernel: [ 53.532498] [] warn_slowpath_common+0x87/0xc0 Nov 5 21:15:45 myhost kernel: [ 53.532585] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532667] [] ? intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532674] [] warn_slowpath_fmt+0x3e/0x60 Nov 5 21:15:45 myhost kernel: [ 53.532757] [] intel_modeset_check_state+0x556/0x910 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532841] [] intel_atomic_commit+0x4cd/0x6a0 [i915] Nov 5 21:15:45 myhost kernel: [ 53.532894] [] ? drm_atomic_check_only+0x1ae/0x600 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532943] [] ? drm_modeset_lock+0x49/0xd0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.532994] [] drm_atomic_commit+0x32/0x60 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533020] [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533070] [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm] Nov 5 21:15:45 myhost kernel: [ 53.533096] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533121] [] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533146] [] drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533229] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] Nov 5 21:15:45 myhost kernel: [ 53.533252] [] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533276] [] output_poll_execute+0x188/0x1c0 [drm_kms_helper] Nov 5 21:15:45 myhost kernel: [ 53.533285] [] process_one_work+0x121/0x3f0 Nov 5 21:15:45 myhost kernel: [ 53.533292] [] worker_thread+0x20a/0x490 Nov 5 21:15:45 myhost kernel: [ 53.533300] [] ? process_one_work+0x3f0/0x3f0 Nov 5 21:15:45 myhost kernel: [ 53.533306] [] kthread+0xa6/0xc0 Nov 5 21:15:45 myhost kernel: [ 53.533315] [] ret_from_kernel_thread+0x21/0x38 Nov 5 21:15:45 myhost kernel: [ 53.533321] [] ? kthread_create_on_node+0x170/0x170 Nov 5 21:15:45 myhost kernel: [ 53.533327] ---[ end trace 361aeae89ccf24ea ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- panic in i915 https://bugs.launchpad.net/bugs/1639506 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
[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.
** Changed in: makedumpfile (Ubuntu) Status: In Progress => Fix Released ** Changed in: makedumpfile (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Yakkety: In Progress Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 == ---Problem Description--- Ubuntu 16.10: kdump is not working in 4.8 kernel. ---Steps to Reproduce--- 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M" 3) sudo update-grub ; reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show 6) echo "c" > /proc/sysrq-trigger Logs root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:/home/ubuntu# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ubuntu:/home/ubuntu# cd root@ubuntu:~# echo "c" > /proc/sysrq-trigger [ 50.733424] sysrq: SysRq : Trigger a crash [ 50.733437] Unable to handle kernel paging request for data at address 0x [ 50.733441] Faulting instruction address: 0xc05af3f4 [ 50.733444] Oops: Kernel access of bad area, sig: 11 [#1] [ 50.733446] SMP NR_CPUS=2048 NUMA pSeries [ 50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic crc32c_vpmsum [ 50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic #12-Ubuntu [ 50.733480] task: c004f7906880 task.stack: c004f7898000 [ 50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: c05af3c0 [ 50.733485] REGS: c004f789b990 TRAP: 0300 Not tainted (4.8.0-11-generic) [ 50.733488] MSR: 80009033 CR: 28242422 XER: 0001 [ 50.733496] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05b04d8 c004f789bc10 c0f46700 0063 GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 GPR08: 0007 0001 0001 GPR12: c05af3c0 c7b31200 2200 GPR16: 10170dc8 0100111c0538 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 310b9624 0001 c0e9fd40 0004 GPR28: c0ea0100 0063 c0e528e8 [ 50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50 [ 50.733539] LR [c05b04d8] __handle_sysrq+0xe8/0x280 [ 50.733541] Call Trace: [ 50.733544] [c004f789bc10] [c09ff9e8] 0xc09ff9e8 (unreliable) [ 50.733548] [c004f789bc30] [c05b04d8] __handle_sysrq+0xe8/0x280 [ 50.733552] [c004f789bcd0] [c05b0c88] write_sysrq_trigger+0x78/0xa0 [ 50.733556] [c004f789bd00] [c03a9a90] proc_reg_write+0xb0/0x110 [ 50.733560] [c004f789bd50] [c030c27c] __vfs_write+0x6c/0xe0 [ 50.733564] [c004f789bd90] [c030d784] vfs_write+0xd4/0x240 [ 50.733567] [c004f789bde0] [c030f49c] SyS_write+0x6c/0x110 [ 50.733571] [c004f789be30] [c00095e0] system_call+0x38/0x108 [ 50.733574] Instruction dump: [ 50.733576] 38427340 7c0802a6 f8010010 f821ffe1 6000 600
[Kernel-packages] [Bug 1637978] Re: take 'P' command from upstream xmon
cherry-picked commit 6dfb54049f9a99b24fe5d5cd2d3af19eadc8f31f
('powerpc/xmon: Add xmon command to dump process/task similar to ps(1)')
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Medium
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Triaged
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Released
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu Zesty)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1637978
Title:
take 'P' command from upstream xmon
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
upstream commit 6dfb54049f9a99b24fe5d5cd2d3af19eadc8f31f contains an
enhancement to xmon to allow listing running tasks. This is vital to
debugging efforts, and so needs to be added to as many release streams
as possible, as soon as possible.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637978/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
peter-biely, could you share your i8kutils settings? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting
I propose to close this. This is clearly fixed with 4.4 on the host, and rolling that out is covered by bug 1602577. It can be closed for auto-package-testing either way as our arm64 nova compute nodes now run 4.4.23. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: auto-package-testing Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] lockups some time after booting Status in Auto Package Testing: Fix Released Status in linux package in Ubuntu: Fix Released 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/auto-package-testing/+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 1603476] Re: Boot failure with EFI stub
I'm marking this verified based on info from the bug description, e.g.,
commit 396f1a08db212138418b38f784e4bbe516d2fdb2 ('x86/efi: Fix boot
failure with EFI stub') fixes the bug.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1603476
Title:
Boot failure with EFI stub
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Bug description:
After updating kernel to 3.13.0-92 system cannot startup with these errors:
Failed to get file info size
Failed to alloc highmem for files
I've found patch fixing it here —
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9&id=396f1a08db212138418b38f784e4bbe516d2fdb2
Works like a charm.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-92-generic 3.13.0-92.139
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
Uname: Linux 3.13.0-92-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andrei 2236 F pulseaudio
/dev/snd/controlC1: andrei 2236 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jul 15 17:41:11 2016
InstallationDate: Installed on 2014-11-26 (596 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro
rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img
RelatedPackageVersions:
linux-restricted-modules-3.13.0-92-generic N/A
linux-backports-modules-3.13.0-92-generic N/A
linux-firmware 1.127.22
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603476/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632462] Re: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632462 Title: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == SRU Justification == Impacts all releases from Trusty through Yakkety http://paste.ubuntu.com/23309548/ From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Tue, 11 Oct 2016 22:18:58 +1100 Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user Debugging a data corruption issue with virtio-net/vhost-net led to the observation that __copy_tofrom_user was occasionally returning a value 16 larger than it should. Since the return value from __copy_tofrom_user is the number of bytes not copied, this means that __copy_tofrom_user can occasionally return a value larger than the number of bytes it was asked to copy. In turn this can cause higher-level copy functions such as copy_page_to_iter_iovec to corrupt memory by copying data into the wrong memory locations. It turns out that the failing case involves a fault on the store at label 79, and at that point the first unmodified byte of the destination is at R3 + 16. Consequently the exception handler for that store needs to add 16 to R3 before using it to work out how many bytes were not copied, but in this one case it was not adding the offset to R3. To fix it, this moves the label 179 to the point where we add 16 to R3. I have checked manually all the exception handlers for the loads and stores in this code and the rest of them are correct (it would be excellent to have an automated test of all the exception cases). Signed-off-by: Paul Mackerras --- arch/powerpc/lib/copyuser_64.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S index f09899e..7b22624 100644 --- a/arch/powerpc/lib/copyuser_64.S +++ b/arch/powerpc/lib/copyuser_64.S @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD) addir3,r3,8 171: 177: +179: addir3,r3,8 370: 372: @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD) 173: 174: 175: -179: 181: 184: 186: -- 2.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571691 Title: linux: MokSBState is ignored Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Ubuntu-4.4.0-20.36 was released with signed module enforcement enabled, but contained no way of disabling secure boot for DKMS. Without these kernel patches it is possible to get your machine in an unbootable state, especially if you don't have a fallback kernel. This patch set implements the ability to disable secure boot on demand from user space (with some password shennaigans). If one boots in secure boot mode and then installs a third party module (such as DKMS), then a dialog is displayed giving the user an option to disable secure boot, thereby also disabling module signature verification. Patch 1/2 is a scaffold patch of which only the GUID macros are actually used. The rest of the code is fenced by CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series. Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3 simply prints a bit more informative state information. Information regarding secure boot and signed module enforcement will appear in the kernel log thusly: 'Secure boot enabled' - normal secure boot operation with signed module enforcement. 'Secure boot MOKSBState disabled' - UEFI Secure boot state has been over-ridden by MOKSBState. No signed module enforcement. In the absense of a 'Secure boot' string assume that secure boot is disabled or does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
@Gábor: The versions at that link are the same versions already in our linux-firmware package, so installing the firmware from that site isn't going to help. Intel's driver is looking for firmware versions that Intel has never released. It's unfortunate that Intel does this with their drivers, but we *cannot* include firmware which hasn't been released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1611124 Title: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 Status in xen: Unknown Status in linux-firmware package in Ubuntu: Invalid Bug description: $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency [...] update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.159 Uname: Linux 4.8.0-040800rc1-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 Date: Mon Aug 8 17:50:38 2016 Dependencies: InstallationDate: Installed on 2015-07-26 (379 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/1611124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639810] [NEW] igb i210 probe of pci device failed with error -2
Public bug reported: [Impact] Intel I210 NIC may show: 'igb: probe of :07:00.0 failed with error -2' Upon boot after power has been completely disconnected. I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. This also happens with the linux 4.9-rc4. [Fix] https://patchwork.ozlabs.org/patch/690464/ This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue. [Test Case] Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Chris J Arges (arges) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639810 Title: igb i210 probe of pci device failed with error -2 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Bug description: [Impact] Intel I210 NIC may show: 'igb: probe of :07:00.0 failed with error -2' Upon boot after power has been completely disconnected. I was able to bisect it down to commit 2a3cdead8b408351fa1e3079b220fa331480ffbc Upon further investigation it was determined that firmware may not properly initialize I347AT4_PAGE_SELECT causing the probe of an igb i210 NIC to fail. This also happens with the linux 4.9-rc4. [Fix] https://patchwork.ozlabs.org/patch/690464/ This patch adds an addition zeroing of this register during igb_get_phy_id to workaround this issue. [Test Case] Completely power down machine with intel igb 210 NIC. Power on and ensure igb device is properly probed and initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593075] Re: linux: Implement secure boot state variables
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593075 Title: linux: Implement secure boot state variables Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: User space needs a way to determine the state of secure boot and MOKSBState. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626222] Re: STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic
Marking verification failed. The fix commit did not fix the panic, nor did it make it any worse. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626222 Title: STC860:alpine-pdq:alpdq5p03: kernel panic when adding vnic Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: Description:Ubuntu 16.04 LTS Linux alpdq5p03 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:35 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Problem Description : When I created a vNIC on alpdq5p03 using U78C7.001.KIC1906-P1-C12-T1 via alpdq5p08 and U78C7.001.KIC1906-P1-C12-T2 via alpdq5p09 as the backing devices I got a kernel panic. [ 129.977324] ibmvnic 3004: Virtual Adapter failed (rc=8) [ 129.977346] Unable to handle kernel paging request for data at address 0x00f1 [ 129.977351] Faulting instruction address: 0xd00010882434 [ 129.977355] Oops: Kernel access of bad area, sig: 11 [#1] [ 129.977359] SMP NR_CPUS=2048 NUMA pSeries [ 129.977364] Modules linked in: ibmvnic rpadlpar_io rpaphp nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag rtc_generic pseries_rng binfmt_misc sunrpc autofs4 ibmvscsi ibmveth [ 129.977392] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-22-generic #40-Ubuntu [ 129.977397] task: c15566b0 ti: c01d8000 task.ti: c15b [ 129.977401] NIP: d00010882434 LR: d00010882420 CTR: c02b25f0 [ 129.977406] REGS: c01db9c0 TRAP: 0300 Not tainted (4.4.0-22-generic) [ 129.977410] MSR: 80009033 CR: 48048224 XER: 2010 [ 129.977422] CFAR: c0008468 DAR: 00f1 DSISR: 4000 SOFTE: 0 GPR00: d00010882420 c01dbc40 d00010894240 GPR04: c01ff4039ee0 001ffdd8 2082 GPR08: c0f9fda8 c0f9fda8 001ffdd8 d000108896e8 GPR12: c02b25f0 ce7e c15eef18 c0f9d678 GPR16: 0001 c01fd3960e18 c01fd3960db0 GPR20: c15b c01fd3960d98 c01fd3960e08 c01fd3960900 GPR24: c01fd3960d88 c01fd39bf000 c01fd39bf048 GPR28: 0100 0200 00f0 c01fd3960900 [ 129.977482] NIP [d00010882434] ibmvnic_free_inflight+0x104/0x330 [ibmvnic] [ 129.977488] LR [d00010882420] ibmvnic_free_inflight+0xf0/0x330 [ibmvnic] [ 129.977492] Call Trace: [ 129.977496] [c01dbc40] [d00010882420] ibmvnic_free_inflight+0xf0/0x330 [ibmvnic] (unreliable) [ 129.977503] [c01dbce0] [d00010887188] ibmvnic_handle_crq+0x3a8/0x2010 [ibmvnic] [ 129.977509] [c01dbda0] [d00010888ea8] ibmvnic_interrupt+0xb8/0x198 [ibmvnic] [ 129.977517] [c01dbe10] [c0130660] handle_irq_event_percpu+0xa0/0x320 [ 129.977523] [c01dbed0] [c0130948] handle_irq_event+0x68/0xc0 [ 129.977528] [c01dbf00] [c0135c2c] handle_fasteoi_irq+0xec/0x2b0 [ 129.977534] [c01dbf30] [c012f844] generic_handle_irq+0x54/0x80 [ 129.977539] [c01dbf60] [c0011320] __do_irq+0x80/0x1d0 [ 129.977545] [c01dbf90] [c0024800] call_do_irq+0x14/0x24 [ 129.977550] [c15b39a0] [c0011508] do_IRQ+0x98/0x140 [ 129.977555] [c15b39f0] [c0002594] hardware_interrupt_common+0x114/0x180 [ 129.977563] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [ 129.977563] LR = check_and_cede_processor+0x34/0x50 [ 129.977570] [c15b3ce0] [c090d9f0] check_and_cede_processor+0x20/0x50 (unreliable) [ 129.977576] [c15b3d40] [c090da94] dedicated_cede_loop+0x74/0x190 [ 129.977582] [c15b3d80] [c090ac20] cpuidle_enter_state+0x160/0x410 [ 129.977588] [c15b3de0] [c0119a88] call_cpuidle+0x78/0xd0 [ 129.977593] [c15b3e20] [c0119e5c] cpu_startup_entry+0x37c/0x480 [ 129.977599] [c15b3ee0] [c000bdcc] rest_init+0xac/0xc0 [ 129.977605] [c15b3f00] [c0ea3f5c] start_kernel+0x53c/0x558 [ 129.977610] [c15b3f90] [c0008c6c] start_here_common+0x20/0xa8 [ 129.977615] Instruction dump: [ 129.977617] e95e0010 7fc3f378 f92a0008 f949 fb9e0010 fbbe0018 480072cd e8410018 [ 129.977626] ebde0010 7fb6f040 3bdefff0 419e00f4 <893e0001> 2f890009 409effb4 7ea3ab78 [ 129.977636] ---[ end trace 79d415687d3074f2 ]--- [ 129.979495] [ 131.979529] Kernel pani
[Kernel-packages] [Bug 1637481] Re: Update linux-firmware in xenial for lts-y
linux-firmware 1.157.5 works well in my testing. Differences in installed firmware files between 1.157.4 and 1.157.5 packages are as expected. ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1637481 Title: Update linux-firmware in xenial for lts-y Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: Fix Committed Bug description: Add/update firmware files to support running yakkety kernels with xenial userspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1637481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634496] Re: proc_keys_show crash when reading /proc/keys
Verified that this is fixed in all -proposed kernels. In precise /proc/keys is not present as a result of CONFIG_KEYS_DEBUG_PROC_KEYS=n, however it's a trivial fix and there's no harm in carrying the patch. ** Tags added: verification-done-precise verification-done-trusty verification-done-vivid verification-done-xenial verification-done- yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634496 Title: proc_keys_show crash when reading /proc/keys Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Running stress-ng /proc test trips the following crash: [ 5315.044206] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8956b1ae [ 5315.044206] [ 5315.044883] CPU: 0 PID: 4820 Comm: Tainted: P OE 4.8.0-25-generic #27-Ubuntu [ 5315.045361] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu2 04/01/2014 [ 5315.045911] 0086 b337622b 8fe574f37c78 8962f5d2 [ 5315.046371] b3405b00 89e83530 8fe574f37d00 8939e71c [ 5315.046841] 8fe50010 8fe574f37d10 8fe574f37ca8 b337622b [ 5315.047305] Call Trace: [ 5315.047457] [] dump_stack+0x63/0x81 [ 5315.047763] [] panic+0xe4/0x226 [ 5315.048049] [] ? proc_keys_show+0x3ce/0x3d0 [ 5315.048398] [] __stack_chk_fail+0x19/0x30 [ 5315.048735] [] proc_keys_show+0x3ce/0x3d0 [ 5315.049072] [] ? key_validate+0x50/0x50 [ 5315.049396] [] ? key_default_cmp+0x20/0x20 [ 5315.049737] [] seq_read+0x102/0x3c0 [ 5315.050042] [] proc_reg_read+0x42/0x70 [ 5315.050363] [] __vfs_read+0x18/0x40 [ 5315.050674] [] vfs_read+0x96/0x130 [ 5315.050977] [] SyS_read+0x55/0xc0 [ 5315.051275] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 5315.051735] Kernel Offset: 0x820 from 0x8100 (relocation range: 0x8000-0xbfff) [ 5315.052563] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8956b1ae [ 5315.052563] "The proc_keys_show function in security/keys/proc.c in the Linux kernel through 4.8.2, when the GNU Compiler Collection (gcc) stack protector is enabled, uses an incorrect buffer size for certain timeout data, which allows local users to cause a denial of service (stack memory corruption and panic) by reading the /proc/keys file." Fix detailed in: https://bugzilla.redhat.com/show_bug.cgi?id=1373966 see: https://bugzilla.redhat.com/attachment.cgi?id=1200212&action=diff To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1634496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set
Verified that this option is set in the proposed xenial kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557776 Title: CONFIG_AUFS_XATTR is not set Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic. The setting CONFIG_AUFS_XATTR is not set. With the previous ubuntu version 15.04 and linux- image-3.19.0-42-generic this setting was compiled as CONFIG_AUFS_XATTR=y Without CONFIG_AUFS_XATTR docker users using the AUFS driver can not work with capabilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630990] Re: include/linux/security.h header syntax error with !CONFIG_SECURITYFS
Downloaded the generated header files and confirmed the fix is in place:
static inline int __securityfs_setup_d_inode(struct inode *dir,
struct dentry *dentry,
umode_t mode, void *data,
const struct file_operations *fops,
const struct inode_operations *iops)
{
return -ENODEV;
}
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1630990
Title:
include/linux/security.h header syntax error with !CONFIG_SECURITYFS
Status in linux package in Ubuntu:
Fix Committed
Status in zfcpdump-kernel package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Fix Committed
Status in zfcpdump-kernel source package in Yakkety:
Fix Released
Bug description:
CC init/main.o
In file included from init/main.c:34:0:
./include/linux/security.h: In function ‘__securityfs_setup_d_inode’:
./include/linux/security.h:1638:42: error: expected declaration specifiers
before ‘)’ token
const struct inode_operations *iops))
^
./include/linux/security.h:1648:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630990/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557776 Title: CONFIG_AUFS_XATTR is not set Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic. The setting CONFIG_AUFS_XATTR is not set. With the previous ubuntu version 15.04 and linux- image-3.19.0-42-generic this setting was compiled as CONFIG_AUFS_XATTR=y Without CONFIG_AUFS_XATTR docker users using the AUFS driver can not work with capabilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632462] Re: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user
** Tags removed: verification-needed-xenial verification-needed-yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632462 Title: [Trusty->Yakkety] powerpc/64: Fix incorrect return value from __copy_tofrom_user Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == SRU Justification == Impacts all releases from Trusty through Yakkety http://paste.ubuntu.com/23309548/ From ca47910e3b549501b6a3ff786174d2f0d4748ccf Mon Sep 17 00:00:00 2001 From: Paul Mackerras Date: Tue, 11 Oct 2016 22:18:58 +1100 Subject: [PATCH] powerpc/64: Fix incorrect return value from__copy_tofrom_user Debugging a data corruption issue with virtio-net/vhost-net led to the observation that __copy_tofrom_user was occasionally returning a value 16 larger than it should. Since the return value from __copy_tofrom_user is the number of bytes not copied, this means that __copy_tofrom_user can occasionally return a value larger than the number of bytes it was asked to copy. In turn this can cause higher-level copy functions such as copy_page_to_iter_iovec to corrupt memory by copying data into the wrong memory locations. It turns out that the failing case involves a fault on the store at label 79, and at that point the first unmodified byte of the destination is at R3 + 16. Consequently the exception handler for that store needs to add 16 to R3 before using it to work out how many bytes were not copied, but in this one case it was not adding the offset to R3. To fix it, this moves the label 179 to the point where we add 16 to R3. I have checked manually all the exception handlers for the loads and stores in this code and the rest of them are correct (it would be excellent to have an automated test of all the exception cases). Signed-off-by: Paul Mackerras --- arch/powerpc/lib/copyuser_64.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/lib/copyuser_64.S b/arch/powerpc/lib/copyuser_64.S index f09899e..7b22624 100644 --- a/arch/powerpc/lib/copyuser_64.S +++ b/arch/powerpc/lib/copyuser_64.S @@ -359,6 +359,7 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD) addir3,r3,8 171: 177: +179: addir3,r3,8 370: 372: @@ -373,7 +374,6 @@ END_FTR_SECTION_IFCLR(CPU_FTR_UNALIGNED_LD_STD) 173: 174: 175: -179: 181: 184: 186: -- 2.7.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Would it be illegal to release it?? Its open source anyway. :/ I imagined that Dell wound not "guarantee" that would work or give any support to those other users. (But we know it 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632894] Re: Revert "If zone is so small that watermarks are the same, stop zone balance" in yakkety
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632894 Title: Revert "If zone is so small that watermarks are the same, stop zone balance" in yakkety Status in linux package in Ubuntu: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: SRU Justification: Impact: This patch was errantly deemed appropriate for yakkety but is not. Returning early might avoid side effects in zone_balanced() that could change behavior. Fix: Revert the patch. Regression potential: This reverts us back to matching upstream, so no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Petr: ad 1: Possibly yes ad 2: yes (I haven't seen anywhere the ISO for download) ad 3: i8kutils seems working, I've tried that. But yes, in case of wrong temp. setting you can damage your CPU/GPU, I'm using it as workaround but I am not satisfied (not sleeping very well) by using that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Triaged Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639600] Re: Number of processes exceeds 1250
This is a file which contains out of ps aux command, lists all the processes running. You can see that lot of kworkers are created. ** Attachment added: "output of ps aux command" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639600/+attachment/4774016/+files/ps_aux.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/1639600 Title: Number of processes exceeds 1250 Status in linux package in Ubuntu: Confirmed Bug description: At times when the linux-image-4.8.0-27 kernel is used it spawns more than 1250 processes and this can be seen using the top command. More amount of kworker processes are being spawned. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uday 5886 F pulseaudio /dev/snd/controlC1: uday 5886 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 6 22:51:39 2016 HibernationDevice: RESUME=UUID=1aa7fbdf-3bda-4de7-8c34-5a6445ce6600 InstallationDate: Installed on 2015-02-14 (631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=9ce2f167-b3df-4db5-bb27-44102031030d ro reboot=acpi RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-14 (22 days ago) dmi.bios.date: 08/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0926J6 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639758] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639758 Title: "Intel(R) Dual Band Wireless AC 7260, REV=0x144" not working reliably Status in linux package in Ubuntu: Confirmed Bug description: On my HP Elitebook 850 G1, the Wireless AC Intel 7260 Wifi card does not work work properly. I notice a lot of disconnections. What I expected to happen: A stable WIFI connection. What happened instead : An unusable WIFI connection. If the problem is not on my hardware, this bug is "Severe" because few users are concerned too: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541845 , - http://askubuntu.com/questions/750064/how-to-change-the-wifi-firmware-in-use , - https://bugzilla.kernel.org/show_bug.cgi?id=91171 , - https://forum.ubuntu-fr.org/viewtopic.php?id=1836861 , - https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_7260_(7260HMW) - https://bbs.archlinux.org/viewtopic.php?id=189103 . My «dmesg | grep iwlwifi»: http://ix.io/1D7a . My /proc/version_signature: Ubuntu 4.4.0-45.66-generic 4.4.21 My "# lspci -vnvn": http://ix.io/1D7e Please tell me how I can help on this ? Feel free to ask me further technical details. Thanks. Raphael. --- HP-EliteBook-850-G1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 HP-EliteBook-850-G1:~$ apt-cache policy linux N: Unable to locate package linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: raph 1844 F...m pulseaudio /dev/snd/controlC1: raph 1844 F pulseaudio /dev/snd/controlC0: raph 1844 F pulseaudio CurrentDesktop: XFCE Date: Mon Nov 7 11:39:50 2016 HibernationDevice: RESUME=UUID=d11a55ee-8bcd-4858-998e-175632ced094 InstallationDate: Installed on 2016-10-28 (9 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 850 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=324f5c1b-d957-45a5-b59a-fe934c2a1bed ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.35 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.57 dmi.chassis.asset.tag: OR6273797 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.35:bd01/26/2016:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009CD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3009CD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773992/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773981/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773993/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773989/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773990/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773991/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773985/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773987/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773988/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773986/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773984/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773982/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773983/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1563110/+attachment/4773980/+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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=66d8ee84-0b79-48ab-9985-b0fc747a8a8a InstallationDate: Installed on 2016-11-06 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=38f20265-ef24-48db-84e7-8615ec9be554 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 Tags: xenial xenial Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1639758] [NEW] "Intel(R) Dual Band Wireless AC 7260, REV=0x144" not working reliably
Public bug reported: On my HP Elitebook 850 G1, the Wireless AC Intel 7260 Wifi card does not work work properly. I notice a lot of disconnections. What I expected to happen: A stable WIFI connection. What happened instead : An unusable WIFI connection. If the problem is not on my hardware, this bug is "Severe" because few users are concerned too: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541845 , - http://askubuntu.com/questions/750064/how-to-change-the-wifi-firmware-in-use , - https://bugzilla.kernel.org/show_bug.cgi?id=91171 , - https://forum.ubuntu-fr.org/viewtopic.php?id=1836861 , - https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_7260_(7260HMW) - https://bbs.archlinux.org/viewtopic.php?id=189103 . My «dmesg | grep iwlwifi»: http://ix.io/1D7a . My /proc/version_signature: Ubuntu 4.4.0-45.66-generic 4.4.21 My "# lspci -vnvn": http://ix.io/1D7e Please tell me how I can help on this ? Feel free to ask me further technical details. Thanks. Raphael. --- HP-EliteBook-850-G1:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 HP-EliteBook-850-G1:~$ apt-cache policy linux N: Unable to locate package linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: raph 1844 F...m pulseaudio /dev/snd/controlC1: raph 1844 F pulseaudio /dev/snd/controlC0: raph 1844 F pulseaudio CurrentDesktop: XFCE Date: Mon Nov 7 11:39:50 2016 HibernationDevice: RESUME=UUID=d11a55ee-8bcd-4858-998e-175632ced094 InstallationDate: Installed on 2016-10-28 (9 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 850 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=324f5c1b-d957-45a5-b59a-fe934c2a1bed ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.35 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.57 dmi.chassis.asset.tag: OR6273797 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.35:bd01/26/2016:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009CD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3009CD10203 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug intel severe wireless xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639758 Title: "Intel(R) Dual Band Wireless AC 7260, REV=0x144" not working reliably Status in linux package in Ubuntu: New Bug description: On my HP Elitebook 850 G1, the Wireless AC Intel 7260 Wifi card does not work work properly. I notice a lot of disconnections. What I expected to happen: A stable WIFI connection. What happened instead : An unusable WIFI connection. If the problem is not on my hardware, this bug is "Severe" because few users are concerned too: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1541845 , - http://askubuntu.com/questions/750064/how-to-change-the-wifi-firmware-in-use , - https://bugzilla.kernel.org/show_bug.cgi?id=91171 , - https://forum.ubuntu-fr.org/viewtopic.php?id=1836861 , - https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_7260_(7260HMW) - https://bbs.archlinux.org/viewtopic.php?id=189103 . My «dmesg | grep iwlwifi»: http://ix.io/1D7a . My /proc/version_signature: Ubuntu 4.4.0-45.66-generic 4.4.21 My "# lspci -vnvn": http://ix.io/1D7e Please tell me how I can help on this ? Feel free to ask me further technical details. Thanks. Raphael. --- HP-EliteBook-850-G1:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 HP-EliteBook-850-G1:~$ apt-cache policy linux N: Unable to locate package linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: raph 1844 F...m pulseaudio /dev/snd/controlC1: raph 1844 F pulseaudio /dev/s
[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log
I have Thinkpad 13 and and am suffering from this pretty badly, system is almost unusable :( $ uname -r 4.8.0-26-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety These just keep on flooding kern.log: [ 935.066369] net_ratelimit: 69 callbacks suppressed [ 935.066383] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.130393] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.194418] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.258393] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.322416] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.386392] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.450411] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.514418] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.578396] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped [ 935.642399] cdc_ether 2-1.1.3:2.0 enx0050b6d89edd: kevent 11 may have been dropped Can anyone suggest at least a workaround if proper fix does not yet exist? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626371 Title: cdc_ether fills kernel log Status in linux package in Ubuntu: Confirmed Bug description: On my Lenovo X1 4th gen with a dock attached: [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been dropped The USB Ethernet device would warn occasionally under the 4.4 kernel. Under the 4.8 kernel, it spams my kernel log so much that I don't get anything else. $ uname -a Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux joel@aurora ~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574047] Re: Lenovo G50-30 laptop freezes randomly
@lumiza I am on 4.8-rc6 kernel its been quite stable for some time and haven't noticed any freezing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574047 Title: Lenovo G50-30 laptop freezes randomly Status in linux package in Ubuntu: Incomplete Bug description: Keyboard or mouse do not work when the system freezes. Have to press power key to shutdown. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] 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: lumiza 1614 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 19:17:13 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=00509798-f59d-4d52-9500-f9a446e82c61 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80G0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=44eeda32-7284-4e84-91ff-72fe3baefb7a 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: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN47WW:bd04/16/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574047/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635424] Re: linux: 3.19.0-74.82 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635424 Title: linux: 3.19.0-74.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-74.82 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
