[Kernel-packages] [Bug 1531768] Re: [arm64] locks up a few minutes after booting
I tried this again yesterday evening, with an up-to-date xenial arm64 image, and lo and behold: Both setting it up and running two parallel loops with calling adt-run over night, and they went through ~ 500 iterations without a hitch. So I suppose this was fixed by some newer kernel, the new glibc, some changed Scalingstack configuration, or the tooth fairy :-) Whatever it was, I close this now as this has become a bit unwieldy. I'll report a new bug if this happens again. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] locks up a few minutes after booting 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/ubuntu/+source/linux/+bug/1531768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1557379] Comment bridged from LTC Bugzilla
--- Comment From santwana.samant...@in.ibm.com 2016-04-13 05:18 EDT--- In the same setup i.e Ubuntu14.04.4, I tried to compile the CUDA-7.5-23 Toolkit, with the NVIDIA Driver "352.88" and after several trials, this issue was no longer reproducible. # dpkg -l cuda Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii cuda 7.5-23 ppc64el CUDA meta-package # cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX ppc64le Kernel Module 352.88 Wed Mar 9 10:18:57 PST 2016 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1) # nvcc -V nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2015 NVIDIA Corporation Built on Tue_Oct_27_14:06:16_CDT_2015 Cuda compilation tools, release 7.5, V7.5.21 # uname -a Linux ubuntu-bug 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:31:44 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="14.04.4 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.4 LTS" VERSION_ID="14.04" The issue seems to be fixed in the NVIDIA Driver version 352.88 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace
[Kernel-packages] [Bug 828731] Re: kdump functionality not working as expected when /boot is a separate partition
still present in trusty! /boot in sda1 and / is on LVM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/828731
Title:
kdump functionality not working as expected when /boot is a separate
partition
Status in kexec-tools package in Ubuntu:
Fix Released
Status in kexec-tools source package in Lucid:
Fix Released
Status in kexec-tools source package in Maverick:
Fix Released
Status in kexec-tools source package in Natty:
Fix Released
Status in kexec-tools source package in Oneiric:
Fix Released
Bug description:
SRU Request for Lucid/Maverick/Natty/Oneiric:
[Impact] - When a server is configured with the /boot as a separate
partition, which is the default configuration when LVM installation is
selected, the kdump mechanism fails systematically.
[Development/Stable Fix] - This has been fixed in the development
version with the addition of the following:
* Backport changes to fix kdump functionality. LP: #828731.
- debian/kdump.initramfs: call /usr/bin/makedumpfile via a chroot command,
so that if makedumpfile is statically linked, we get proper library
resolution. Thanks to Louis Bouchard for
the patch. LP: #785425.
- debian/kdump.initramfs: handle the possibility that /usr, /boot, or
/var is on a separate filesystem and needs to be manually mounted before
calling makedumpfile. LP: #828731.
- Depend on makedumpfile, without which the initramfs script doesn't work.
- Fix an unnecessary bashism.
- Only install the kdump initramfs script and depend on makedumpfile on
architectures that makedumpfile supports.
[Test Case] - See 'how to reproduce' below.
[Regression Potential] - Need to ensure kdump works correctly in backported
versions.
--
Description : Ubuntu 10.04.2
Release : 10.04
When a server is configured with the /boot as a separate partition,
which is the default configuration when LVM installation is selected,
the kdump mechanism fails systematically.
This is caused by the fact that the ./scripts/init-bottom/0_kdump
script that is loaded into the initrd.img file make the assumption
that /boot is _ALWAYS_ a directory which contains the vmcoreinfo-$KVER
file. The bug is contained within the following code :
KVER="`uname -r`"
INFO="$rootmnt/boot/vmcoreinfo-$KVER"
CRASHFILE="$rootmnt/var/crash/vmcore"
MAKEDUMPFILE="$rootmnt/usr/bin/makedumpfile"
LOG="$rootmnt/var/crash/vmcore.log"
VMCORE="/proc/vmcore"
# Check that this is a kexec kernel.
grep -q kdump_needed /proc/cmdline || exit 0
# Do NOT exit the script after this point, or the system will start
# booting inside the crash kernel.
. ./scripts/functions
# Make sure makedumpfile assumptions are satisfied.
while ! test -e "$INFO"; do
panic "kdump: Missing $INFO"
done
while ! test -x "$MAKEDUMPFILE"; do
panic "kdump: Missing $MAKEDUMPFILE"
done
The test 'while !test -e "$INFO";do' fails if /boot is a separate
partition.
Reproducible: 100%
How to Reproduce :
Pre-requisite : a system or VM installed with LVM and /boot as a
separate partition (default option for LVM installation)
1) install the linux-crashdump package & dependancies
2) Increase the crashkernel= parameter to 128M if the RAM is below 2048M (LP
Bug#785394) in /etc/grub.d/10_linux
3) Run sudo update-grub
4) Reboot the system
5) Force a panic with "echo c > /proc/sysrq-trigger
The system will reboot to the kexec kernel with complete network
access enabled :
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.32-28-server root=/dev/mapper/Lucid--lvmS-root ro
kdump_needed maxcpus=1 irqpoll reset_devices memmap=exactmap memmap=640K@0K
memmap=130412K@33408K elfcorehdr=163820K
Workaround:
Copy the content of the /boot partition into the /boot directory. This is
only valid until the next upgrade of the "linux-image-{version}" package.
How to workaround :
6) Reboot the system
7) Copy the content of the /boot partition into the /boot directory
# df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda1 233191 17563203187 8% /boot
# sudo umount /boot
# sudo mount /dev/vda1 /mnt
# sudo cp -pr /mnt/* /boot
# sudo umount /mnt
# sudo mount -a
# sudo echo c > /proc/sysrq-tgrigger
The system will correctly generate a crash dump
# find /var/crash
/var/crash
/var/crash/linux-image-2.6.32-28-server.0.crash
ProblemType: Bug
DistroRelease: Ubuntu 10.04.02
Package: kexec-tools-1-2.0.1-1ubuntu3
Uname: Linux 2.6.32-28-server x86_64
Architecture: amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/828731/+subscriptions
--
Ma
[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG
Same error here on a brand new ASUS BU201LA laptop ( I did the mistake to not check its compatibility in advance ) ... :-( 02:00.0 Unassigned class [ff00]: Device 1aea:6601 Subsystem: Device 0001:0001 Hope the bug will be fixed, SD reader is key for me. Have a nice day -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270676 Title: SD Card Reader broken on UX302LG Status in linux package in Ubuntu: Triaged Bug description: SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG laptop. USB readers work without problem. Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood). Nothing is listed in lsusb -v that could be the reader. Nohting is listed in lspci -k -vv -nnn. Nothing in acpi_listen. Nothing in kern.log etc. According to (select "Windows 8" then "Card Reader") : http://support.asus.com/download.aspx?SLanguage=en&p=3&s=597&m=UX302LG&os=&hashedid=GEZaY8oaj8oSlQ3U Reader vendor is : Alcor Multi-Card Reader Driver http://www.pcidatabase.com/vendor_details.php?id=1672 There is only one device that is "Unassigned class" 1aea:6601 but searching this online only pops up my other bug reports (sigh) and vendor is unassigned on pcidatabase.com. But...Downloading the 14M Win driver for the reader, vendor id 1aea and device id 6601 is present at multiple instances : [DeviceList.NTamd64] ; For XP and later %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea&DEV_6601 Also there is mention of _Gen instance in the .inf, might point to a "Generic" alternative ? [DeviceList_Gen.NTamd64] ; For XP and later %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b&DEV_0ef6 This does point to something totally different online 105b:0ef6 points to some Realtek HD Audio device... --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231) Package: linux (not installed) Tags: trusty Uname: Linux 3.13.0-031300-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231) MachineType: ASUSTeK COMPUTER INC. UX302LG Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset plymouth:debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 RelatedPackageVersions: linux-restricted-modules-3.13.0-4-generic N/A linux-backports-modules-3.13.0-4-generic N/A linux-firmware1.121 Tags: trusty Uname: Linux 3.13.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549187] Re: dell_wmi: Unknown key e??? pressed
This is fixed upstream. https://github.com/torvalds/linux/commit/a464afb9581f6a9eabce8a4aa0c70cb71e6bf4d9 while the commitmessage mentions skylake, it also applies to braodwell XPS 13 (9343) and correction to the initial report. > Fn+Esc -> key 151 -> Lock computer nope, that is locking the Fn key (the symbol on the key also is a padlock with a "Fn" written inside it) > Some special keys are not handled they are handled, they do what they are supposed to do, but independent from the 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/1549187 Title: dell_wmi: Unknown key e??? pressed Status in linux package in Ubuntu: Triaged Bug description: Some special keys are not handled on Ubuntu 15.10 Wily and Dell XPS 15 9550 Feb 24 10:10:14 XPS15-GQA kernel: [ 4280.734355] dell_wmi: Unknown key 153 pressed Feb 24 10:10:16 XPS15-GQA kernel: [ 4282.893413] dell_wmi: Unknown key 152 pressed Feb 24 10:10:30 XPS15-GQA kernel: [ 4296.263752] dell_wmi: Unknown key 151 pressed - Fn+Esc -> key 151 -> Lock computer - Fn+F10 -> key 152 -> keyboard backlighting on/off - Fn+Print Screen -> key 153 -> Wifi on/off --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gquintana 1746 F pulseaudio /dev/snd/controlC0: gquintana 1746 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=2e069a2b-037f-4058-89b1-6e221da4046d InstallationDate: Installed on 2016-01-31 (23 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=3ecb2c05-ad6c-4d9d-9356-48c6991f0226 ro quiet splash nouveau.modeset=0 vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 11/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.07 dmi.board.name: 0X2P13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.07:bd11/02/2015:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569831] [NEW] Laptop does not resume after suspend (blackscreen).
Public bug reported: I have installed OS multiple times. I have to manually install the BCM driver. After installing the bcmwl-kernal-source the laptop will suspend, but not resume after. If I disable the external driver, the suspend resume works again. I have tried with a variety of different configs. Network card is BCM4352 [14e4-43b1](rev03) When I try to resume the laptop turns on, but screen never turns on. I've tried to the shortuts to turn the screen back on. I'm using NVIDIA drivers, but even if I use the generic drivers the laptop will not resume. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 13 11:05:08 2016 InstallationDate: Installed on 2016-03-05 (39 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1569831 Title: Laptop does not resume after suspend (blackscreen). Status in bcmwl package in Ubuntu: New Bug description: I have installed OS multiple times. I have to manually install the BCM driver. After installing the bcmwl-kernal-source the laptop will suspend, but not resume after. If I disable the external driver, the suspend resume works again. I have tried with a variety of different configs. Network card is BCM4352 [14e4-43b1](rev03) When I try to resume the laptop turns on, but screen never turns on. I've tried to the shortuts to turn the screen back on. I'm using NVIDIA drivers, but even if I use the generic drivers the laptop will not resume. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 13 11:05:08 2016 InstallationDate: Installed on 2016-03-05 (39 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1569831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566471] Re: kernel oops: NULL pointer dereference in nfs_inode_attach_open_context+0x37/0x70 [nfs]
I also experience this problem using the Xenial kernel 4.4.0-18.34~14.04.1 on Ubuntu 14.04. I can even reproduce it as a non-root user by creating an overlay mount inside a user namespace. After mounting an overlay over an NFS mount, I can successfully traverse existing directories and create, write, read, and remove new files. As soon as I try to read an existing file (from the lower layer NFS mount), the application that attempts the read dies and the syslog shows the kernel bug. The system continues running afterwards. Furthermore, a similar crash occurs for NFS 4 mounts: Apr 13 09:49:20 tortuga kernel: [ 4611.794037] BUG: unable to handle kernel NULL pointer dereference at 0160 Apr 13 09:49:20 tortuga kernel: [ 4611.794144] IP: [] nfs4_file_open+0xcd/0x1d0 [nfsv4] Apr 13 09:49:20 tortuga kernel: [ 4611.794202] PGD 414777067 PUD 302045067 PMD 0 Apr 13 09:49:20 tortuga kernel: [ 4611.794233] Oops: [#1] SMP Apr 13 09:49:20 tortuga kernel: [ 4611.794255] Modules linked in: overlay rpcsec_gss_krb5 nfsv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_CHECKSUM iptable_mangle xt_tcpudp ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 bridge stp llc bnep rfcomm bluetooth nfsd auth_rpcgss nfs_acl nfs binfmt_misc lockd grace sunrpc fscache dm_crypt input_leds joydev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec hid_generic snd_hda_core snd_hwdep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas snd_pcm kvm_intel snd_seq_midi snd_seq_midi_event kvm snd_rawmidi usbhid dm_multipath hid snd_seq snd_seq_device irqbypass crct10dif_pclmul snd_timer crc32_pclmul serio_raw snd aesni_intel mei_me aes_x86_64 soundcore lrw gf128mul mei glue_helper ablk_helper shpchp cryptd ppdev msr lpc_ich cpuid pa rport_pc 8250_fintek mac_hid lp parport amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops e1000e drm ahci psmouse ptp libahci pps_core fjes video [last unloaded: ipmi_msghandler] Apr 13 09:49:20 tortuga kernel: [ 4611.794983] CPU: 4 PID: 14306 Comm: cat Not tainted 4.4.0-18-generic #34~14.04.1-Ubuntu Apr 13 09:49:20 tortuga kernel: [ 4611.795027] Hardware name: Dell Inc. OptiPlex 790/0HY9JP, BIOS A07 09/10/2011 Apr 13 09:49:20 tortuga kernel: [ 4611.795067] task: 8800a9822940 ti: 8803e9d3 task.ti: 8803e9d3 Apr 13 09:49:20 tortuga kernel: [ 4611.795108] RIP: 0010:[] [] nfs4_file_open+0xcd/0x1d0 [nfsv4] Apr 13 09:49:20 tortuga kernel: [ 4611.795171] RSP: 0018:8803e9d33c18 EFLAGS: 00010246 Apr 13 09:49:20 tortuga kernel: [ 4611.795200] RAX: RBX: 8803e7d78700 RCX: 8803e9d33c38 Apr 13 09:49:20 tortuga kernel: [ 4611.795239] RDX: 8000 RSI: 8803f09a8540 RDI: 88041873a148 Apr 13 09:49:20 tortuga kernel: [ 4611.795278] RBP: 8803e9d33cb0 R08: R09: 88041cc03800 Apr 13 09:49:20 tortuga kernel: [ 4611.795317] R10: c06c9230 R11: ea000f9f5e00 R12: Apr 13 09:49:20 tortuga kernel: [ 4611.795356] R13: 880317e9b680 R14: R15: 88041873a148 Apr 13 09:49:20 tortuga kernel: [ 4611.795396] FS: 7f8678c77740() GS:88041d30() knlGS: Apr 13 09:49:20 tortuga kernel: [ 4611.795440] CS: 0010 DS: ES: CR0: 80050033 Apr 13 09:49:20 tortuga kernel: [ 4611.795472] CR2: 0160 CR3: 000374f2b000 CR4: 000406e0 Apr 13 09:49:20 tortuga kernel: [ 4611.795510] Stack: Apr 13 09:49:20 tortuga kernel: [ 4611.795523] 8803850868f0 8000 880317d39740 8803f09a8540 Apr 13 09:49:20 tortuga kernel: [ 4611.795568] 88038000 0001 8803850868f0 Apr 13 09:49:20 tortuga kernel: [ 4611.795612] 8803850868f0 8803e7d78700 8803e7d78710 Apr 13 09:49:20 tortuga kernel: [ 4611.795656] Call Trace: Apr 13 09:49:20 tortuga kernel: [ 4611.795677] [] do_dentry_open+0x227/0x320 Apr 13 09:49:20 tortuga kernel: [ 4611.795720] [] ? nfs4_file_fsync+0x180/0x180 [nfsv4] Apr 13 09:49:20 tortuga kernel: [ 4611.795757] [] vfs_open+0x57/0x60 Apr 13 09:49:20 tortuga kernel: [ 4611.795787] [] path_openat+0x1ad/0x1310 Apr 13 09:49:20 tortuga kernel: [ 4611.795820] [] do_filp_open+0x7e/0xd0 Apr 13 09:49:20 tortuga kernel: [ 4611.795852] [] ? cp_new_stat+0x13d/0x160 Apr 13 09:49:20 tortuga kernel: [ 4611.795885] [] ? __alloc_fd+0x46/0x180 Apr 13 09:49:20 tortuga kernel: [ 4611.795916] [] do_sys_open+0x129/0x270 Apr 13 09:49:20 tortuga kernel: [ 4611.795947] [] SyS_open+0x1e/0x20 Apr 13 09:49:20 tortuga kernel: [ 4611.795978] [] entry_SYSCALL_64_fastpath+0x16/0x75 Apr 13 09:49:20 tortuga kernel: [ 4611.796013] Code: 00 00 49 8b 47 28 45 31 c0 48 8d 4d 88 8b 95 7
[Kernel-packages] [Bug 1557379] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit
Marking Fixed Released as this bug appears to be fixed according to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557379/comments/7 ** Changed in: linux (Ubuntu) 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/1557379 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] noticed during compilation of CUDA Toolkit Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - SANTWANA SAMANTRAY - 2016-01-18 05:50:42 == During compilation of NVIDIA_CUDA-7.5 Toolkit Samples, in Ubuntu14.04.04 Guest, the below BUG is noticed. [1.077464] NVRM: loading NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 [1.211127] init: failsafe main process (498) killed by TERM signal [1.307135] audit: type=1400 audit(1453110711.213:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=697 comm="apparmor_parser" [1.307458] audit: type=1400 audit(1453110711.213:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=695 comm="apparmor_parser" [1.307467] audit: type=1400 audit(1453110711.213:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=695 comm="apparmor_parser" [1.560244] init: plymouth-upstart-bridge main process ended, respawning [ 1600.099759] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [cicc:15164] [ 1600.100531] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1600.100611] CPU: 0 PID: 15164 Comm: cicc Tainted: P OE 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1600.100613] task: c390d3e0 ti: c39c8000 task.ti: c39c8000 [ 1600.100615] NIP: 103eadc8 LR: 103eb5e0 CTR: 103eb5a0 [ 1600.100622] REGS: c39cbea0 TRAP: 0901 Tainted: P OE (4.2.0-23-generic) [ 1600.100623] MSR: 80010280f033 CR: 4848 XER: [ 1600.100646] CFAR: 103eb5dc SOFTE: 1 [ 1600.100646] GPR00: 103eb5e0 3fffc0d01300 10ed2838 01000459e250 [ 1600.100646] GPR04: 0061 0100098e3ae0 [ 1600.100646] GPR08: 090c 0100045d8c00 01000459e308 07ff [ 1600.100646] GPR12: 4824 1006d750 [ 1600.100657] NIP [103eadc8] 0x103eadc8 [ 1600.100658] LR [103eb5e0] 0x103eb5e0 [ 1600.100659] Call Trace: [ 1672.099724] NMI watchdog: BUG: soft lockup - CPU#4 stuck for 32s! [cicc:15182] [ 1672.100995] Modules linked in: nvidia(POE) drm pseries_rng rtc_generic [ 1672.101033] CPU: 4 PID: 15182 Comm: cicc Tainted: P OEL 4.2.0-23-generic #28~14.04.1-Ubuntu [ 1672.101035] task: c0009c5328a0 ti: c306 task.ti: c306 [ 1672.101037] NIP: 11266b0c LR: 11266af4 CTR: 11266a70 [ 1672.101038] REGS: c3063ea0 TRAP: 0901 Tainted: P OEL (4.2.0-23-generic) [ 1672.101039] MSR: 80010280f033 CR: 28222422 XER: [ 1672.101046] CFAR: 112637b4 SOFTE: 1 [ 1672.101046] GPR00: 11266af4 37275860 11392800 01001e07e370 [ 1672.101046] GPR04: 0100 11389fb0 ff0c 01001e07e360 [ 1672.101046] GPR08: 0051 0001 01001b64b230 [ 1672.101046] GPR12: 2200 1006d750 [ 1672.101055] NIP [11266b0c] 0x11266b0c [ 1672.101056] LR [11266af4] 0x11266af4 [ 1672.101057] Call Trace: The nouveau modules are disabled, and nvidia drivers are loaded in the guest. # lsmod | grep nvidia nvidia 11484644 0 drm 447733 2 nvidia After downloading the CUDA Developer tool-kit, during the compilation the BUG is noticed. This issue is intermittently occurring, at some instances this issues isn't noticed. == Guest Details == # uname -a Linux ubuntu 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux # lspci -nn 00:01.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000] 00:02.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] 00:03.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001] 00:04.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002] 00:05.0 3D controller [0302]: NVIDIA Corporation GK210GL [Tesla K80] [10de:102d] (rev a1) # cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX ppc64le Kernel Module 352.39 Fri Aug 14 17:10:41 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubun
[Kernel-packages] [Bug 1569852] [NEW] git-ubuntu-log should also parse CVE# and display them on title lines
Public bug reported: For example if we have CVE-2015-1234567 that is fixed by two patches it will look like: * The-sky-is-falling security fix. (CVE-2015-1234567) - crypto/ancient: Disallow use of ROT13 - Documentation: Added marketing materials ** Affects: linux (Ubuntu) Importance: Low Assignee: Andy Whitcroft (apw) Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569852 Title: git-ubuntu-log should also parse CVE# and display them on title lines Status in linux package in Ubuntu: Triaged Bug description: For example if we have CVE-2015-1234567 that is fixed by two patches it will look like: * The-sky-is-falling security fix. (CVE-2015-1234567) - crypto/ancient: Disallow use of ROT13 - Documentation: Added marketing materials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569852] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1569852 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/1569852 Title: git-ubuntu-log should also parse CVE# and display them on title lines Status in linux package in Ubuntu: Triaged Bug description: For example if we have CVE-2015-1234567 that is fixed by two patches it will look like: * The-sky-is-falling security fix. (CVE-2015-1234567) - crypto/ancient: Disallow use of ROT13 - Documentation: Added marketing materials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569852] Re: git-ubuntu-log should also parse CVE# and display them on title lines
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569852 Title: git-ubuntu-log should also parse CVE# and display them on title lines Status in linux package in Ubuntu: Triaged Bug description: For example if we have CVE-2015-1234567 that is fixed by two patches it will look like: * The-sky-is-falling security fix. (CVE-2015-1234567) - crypto/ancient: Disallow use of ROT13 - Documentation: Added marketing materials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
In my own case it don't work. It's impossible to pair the MX4 (OTA-10.1) to "Nissan Connect" bluetooth. Also, it's now impossible to forget the "Nissan Connect" paired before. The "forget" button isn't cliccable (see pictures attached). You can find my bluetooth log file (with OTA-9) attached at the message number 22 ( https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/comments/22 ). If needed, I can prepare a new log file. ** Attachment added: "MX4_bluetooth_car_pair_problem.zip" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4635443/+files/MX4_bluetooth_car_pair_problem.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569870] [NEW] [Dell Inc. Latitude E6540] hibernate/resume failure
Public bug reported: null ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yaantech 2353 F pulseaudio /dev/snd/controlC1: yaantech 2353 F pulseaudio Date: Wed Apr 13 01:46:18 2016 DuplicateSignature: hibernate/resume:Dell Inc. Latitude E6540:A16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=2c9324c7-4aa7-44d9-bd4f-0a9a3b016ba7 InstallationDate: Installed on 2016-04-06 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) InterpreterPath: /usr/bin/python3.5 MachineType: Dell Inc. Latitude E6540 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--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-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. Latitude E6540] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops hibernate resume 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/1569870 Title: [Dell Inc. Latitude E6540] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: null ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yaantech 2353 F pulseaudio /dev/snd/controlC1: yaantech 2353 F pulseaudio Date: Wed Apr 13 01:46:18 2016 DuplicateSignature: hibernate/resume:Dell Inc. Latitude E6540:A16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=2c9324c7-4aa7-44d9-bd4f-0a9a3b016ba7 InstallationDate: Installed on 2016-04-06 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) InterpreterPath: /usr/bin/python3.5 MachineType: Dell Inc. Latitude E6540 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--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-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. Latitude E6540] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569870/+subscriptions -- Mailing list: https://launc
[Kernel-packages] [Bug 1569870] Re: [Dell Inc. Latitude E6540] hibernate/resume failure
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569870 Title: [Dell Inc. Latitude E6540] hibernate/resume failure Status in linux package in Ubuntu: New Bug description: null ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yaantech 2353 F pulseaudio /dev/snd/controlC1: yaantech 2353 F pulseaudio Date: Wed Apr 13 01:46:18 2016 DuplicateSignature: hibernate/resume:Dell Inc. Latitude E6540:A16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=2c9324c7-4aa7-44d9-bd4f-0a9a3b016ba7 InstallationDate: Installed on 2016-04-06 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) InterpreterPath: /usr/bin/python3.5 MachineType: Dell Inc. Latitude E6540 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--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-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. Latitude E6540] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569870] 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/1569870 Title: [Dell Inc. Latitude E6540] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: null ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yaantech 2353 F pulseaudio /dev/snd/controlC1: yaantech 2353 F pulseaudio Date: Wed Apr 13 01:46:18 2016 DuplicateSignature: hibernate/resume:Dell Inc. Latitude E6540:A16 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=2c9324c7-4aa7-44d9-bd4f-0a9a3b016ba7 InstallationDate: Installed on 2016-04-06 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) InterpreterPath: /usr/bin/python3.5 MachineType: Dell Inc. Latitude E6540 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic.efi.signed root=/dev/mapper/ubuntu--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-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [Dell Inc. Latitude E6540] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd09/01/2015:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I can confirm that it is not working for me either. However, there is a small difference from the previous tries: Now the car system asks for the pin code, and it takes 4-5 seconds before failing, whereas previously it instantly failed. I will report back later with the debug log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 15.04-15.10 freezes totally
I have same problem. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1503731 Title: 8086:0f31 Ubuntu 14.04-15.10 freezes totally Status in linux package in Ubuntu: Confirmed Bug description: Ever since I first installed 15.04 back in April/May on my new DELL Inspiron 3646 I have experienced frequent(daily/every-other- day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.). I have determined that the issue is related to the 'i915' driver in relation to my GPU. I'm currently using intel-linux-graphics- installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics with similar results (maybe a little better than the stock i915 stack in 15.04). WORKAROUND: Use kernel boot parameter: intel_idle.max_cstate=1 I have gained _significant_ improvements in reliability / stability by using parameters in the i915 module: /etc/modprobe.d/i915.conf: options i915 semaphores=1 and / or /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable" and / or /usr/share/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "1" EndSection and / or Disable "Intel Virtualization Technologies" in the BIOS. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CompositorRunning: None Date: Wed Oct 7 09:32:47 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:068d] InstallationDate: Installed on 2015-09-17 (19 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmGreeterLog: ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: upstart ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed to open file '/home/chris/.face': No such file or directory MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0V6D8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09: dmi.product.name: Inspiron 3646 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Oct 6 20:05:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 990 vendor ACR xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 15.04-15.10 freezes totally
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1503731 Title: 8086:0f31 Ubuntu 14.04-15.10 freezes totally Status in linux package in Ubuntu: Confirmed Bug description: Ever since I first installed 15.04 back in April/May on my new DELL Inspiron 3646 I have experienced frequent(daily/every-other- day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.). I have determined that the issue is related to the 'i915' driver in relation to my GPU. I'm currently using intel-linux-graphics- installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics with similar results (maybe a little better than the stock i915 stack in 15.04). WORKAROUND: Use kernel boot parameter: intel_idle.max_cstate=1 I have gained _significant_ improvements in reliability / stability by using parameters in the i915 module: /etc/modprobe.d/i915.conf: options i915 semaphores=1 and / or /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable" and / or /usr/share/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "1" EndSection and / or Disable "Intel Virtualization Technologies" in the BIOS. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CompositorRunning: None Date: Wed Oct 7 09:32:47 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:068d] InstallationDate: Installed on 2015-09-17 (19 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmGreeterLog: ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: upstart ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed to open file '/home/chris/.face': No such file or directory MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0V6D8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09: dmi.product.name: Inspiron 3646 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Oct 6 20:05:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 990 vendor ACR xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1503731] Re: 8086:0f31 Ubuntu 14.04-15.10 freezes totally
** Summary changed: - 8086:0f31 Ubuntu 15.04-15.10 freezes totally + 8086:0f31 Ubuntu 14.04-15.10 freezes totally -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1503731 Title: 8086:0f31 Ubuntu 14.04-15.10 freezes totally Status in linux package in Ubuntu: Confirmed Bug description: Ever since I first installed 15.04 back in April/May on my new DELL Inspiron 3646 I have experienced frequent(daily/every-other- day)complete lockups(cannot even switch to console(Alt-F1,F2,etc.). I have determined that the issue is related to the 'i915' driver in relation to my GPU. I'm currently using intel-linux-graphics- installer_1.2.0-0intel1_amd64.deb from https://01.org/linuxgraphics with similar results (maybe a little better than the stock i915 stack in 15.04). WORKAROUND: Use kernel boot parameter: intel_idle.max_cstate=1 I have gained _significant_ improvements in reliability / stability by using parameters in the i915 module: /etc/modprobe.d/i915.conf: options i915 semaphores=1 and / or /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_pstate=disable" and / or /usr/share/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "1" EndSection and / or Disable "Intel Virtualization Technologies" in the BIOS. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CompositorRunning: None Date: Wed Oct 7 09:32:47 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:068d] InstallationDate: Installed on 2015-09-17 (19 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmGreeterLog: ** (lightdm-gtk-greeter:1005): WARNING **: [PIDs] Failed to execute command: upstart ** (lightdm-gtk-greeter:1005): WARNING **: Failed to load user image: Failed to open file '/home/chris/.face': No such file or directory MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=ef22be35-6f79-4356-be42-2689d1de0378 ro quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0V6D8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0V6D8J:rvrA00:cvnDellInc.:ct3:cvrA09: dmi.product.name: Inspiron 3646 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Oct 6 20:05:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 990 vendor ACR xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569924] [NEW] linux: Add UEFI keyring for externally signed modules
Public bug reported: https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1569924 Title: linux: Add UEFI keyring for externally signed modules Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
I should also mention that the original command used will work if we specify which cpu type to use: qemu-system-ppc64 -m 256 \ -cpu POWER8 \ -display none -nographic \ -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 \ -machine pseries \ -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio \ -drive file=seed.iso,if=virtio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU: Confirmed Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex
[Kernel-packages] [Bug 1554613] Re: screen flickering on XPS13 9350
Is there anything i can do to support? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: screen flickering on XPS13 9350 Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: see LP: #1552304 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
Build target was changed to P8 starting with Xenial. Previously it had been a P7 target. I would expect Xenial kernel to have problems booting on a P7 model. IMO this kernel bug is invalid. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU: Confirmed Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.0
[Kernel-packages] [Bug 1270844] Re: Marvell 88SE9485 SAS/SATA 6Gb/s controller patch
Direct repo link http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=254d48a09324c5748487db2f349fc7b32b8d1d76 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1270844 Title: Marvell 88SE9485 SAS/SATA 6Gb/s controller patch Status in linux package in Ubuntu: Triaged Bug description: Hi, The following patch solves the problem of the 88SE9485 controller not being recognized by the kernel: http://www.spinics.net/lists/linux-scsi/msg51816.html Tested and working on Ubuntu 13.10. It was suggested to me on #linux on Freenode that I contact the kernel maintainers for the distribution that I use. I hope this is the right place for that. Best, Maarten Veenstra --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 15 01:42 seq crw-rw 1 root audio 116, 33 Jan 15 01:42 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=d9d3c390-c2f6-4ba3-9195-c8781d73ba11 InstallationDate: Installed on 2013-12-11 (40 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Supermicro X10SLH-F/X10SLM+-F MarkForUpload: True NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3601dba4-5ddf-4127-84a4-e18b80765d04 ro ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: Error: [Errno 2] No such file or directory Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 07/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10SLH-F/X10SLM+-F dmi.board.vendor: Supermicro dmi.board.version: L� �. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1:bd07/19/2013:svnSupermicro:pnX10SLH-F/X10SLM+-F:pvr0123456789:rvnSupermicro:rnX10SLH-F/X10SLM+-F:rvrL.:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SLH-F/X10SLM+-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
** Changed in: qemu Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU: Invalid Status in linux package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,2:speed=auto,duplex=auto,csarch,000.000.000.000,,000
[Kernel-packages] [Bug 1400319] Re: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10
** Summary changed: - [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10 and 15.04 + [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1400319 Title: [Hyper-V] Kernel panic not functional on 32bit Ubuntu 14.10, 15.04, and 15.10 Status in kexec-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in kexec-tools source package in Wily: Confirmed Status in linux source package in Wily: Confirmed Bug description: While testing the final build of 14.10 32bit we found that kernel panic cannot be activated for an installation on a Hyper-V VM. Repro rate: 100% Repro details: Hyper-V: Server 2012 R2 VM: Ubuntu 14.10 32bit Kdump is enabled in the config file at /etc/default/kdump-tools Different crashkernel values used in grub.cfg – 128M-:64M | 256M-:128m | 384M-:256M VM settings: 2 cores, various RAM sizes attempted: 1, 2 or 4 GB – this in combination with the values for crashkernel. Trying to start the kdump service: root@ubuntu1410i386:~# /etc/init.d/kdump-tools start Starting kdump-tools: Could not find a free area of memory of 0x9f000 bytes... locate_hole failed * failed to load kdump kernel --- root@ubuntu1410i386:~# cat /sys/kernel/kexec_crash_loaded 0 If the conversion from hex to dec is right, the mentioned memory mapping of 0x9f000 bytes is equal to 651264 (bytes), so under 1MB. This is not then related to the RAM allocation nor the crashkernel value used. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=5a5d0aa4-b8ee-4bf7-b1b9-761b7d1550b6 InstallationDate: Installed on 2014-10-31 (37 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release i386 (20141022.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=83fb481a-8898-4adc-bf31-4e160f5f0ce8 ro crashkernel=128M-:64M ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: Error: [Errno 2] No such file or directory Tags: utopic Uname: Linux 3.16.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: Dec 8 08:16:46 ubuntu1410i386 dhclient: DHCPREQUEST of 10.226.59.102 on eth0 to 10.184.232.100 port 67 (xid=0x4b67ffa3) Dec 8 08:16:46 ubuntu1410i386 dhclient: DHCPACK of 10.226.59.102 from 10.184.232.100 Dec 8 08:16:47 ubuntu1410i386 dhclient: bound to 10.226.59.102 -- renewal in 13914 seconds. Dec 8 10:10:47 ubuntu1410i386 kernel: [1840786.031060] init: tty1 main process ended, respawning _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7176-0455-3377-8479-3268-6677-66 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1400319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570024] [NEW] package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: upgrading to ubuntu wily ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 5463 F pulseaudio /dev/snd/seq:timidity 10140 F timidity Date: Wed Apr 13 15:29:10 2016 DuplicateSignature: package:linux-image-4.2.0-35-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=7ff76835-7221-42f5-ade0-a3e31f3b9834 InstallationDate: Installed on 2012-11-28 (1232 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Acer TravelMate 4050 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=UUID=4be25730-2dd3-432b-8342-1f3bd4c07ecb 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: grub-pc 2.02~beta2-29ubuntu0.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-04-13 (0 days ago) dmi.bios.date: 08/10/2004 dmi.bios.vendor: ACER dmi.bios.version: V1.20 dmi.board.name: TravelMate 4050 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: temp dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnACER:bvrV1.20:bd08/10/2004:svnAcer:pnTravelMate4050:pvr290:rvnAcer:rnTravelMate4050:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 4050 dmi.product.version: 290 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570024 Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: New Bug description: upgrading to ubuntu wily ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 5463 F pulseaudio /dev/snd/seq:timidity 10140 F timidity Date: Wed Apr 13 15:29:10 2016 DuplicateSignature: package:linux-image-4.2.0-35-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=7ff76835-7221-42f5-ade0-a3e31f3b9834 InstallationDate: Installed on 2012-11-28 (1232 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Acer TravelMate 4050 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=UUID=4be25730-2dd3-432b-8342-1f3bd4c07ecb 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: grub-pc 2.02~beta2-29ubuntu0.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-04-13 (0 days ago) dmi.bios.date: 08/10/2004 dmi.bios.vendor: ACER dmi.bios.version: V1.20 dmi.board.name: TravelMate 4050 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: temp dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnACER:bvrV1.20:bd08/10/2004:svnAcer:pnTravelMate4050:pvr290:rvnAcer:rnTravelMate4050:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 4050 dmi.product.version: 290 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570
[Kernel-packages] [Bug 1570024] Re: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570024 Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: New Bug description: upgrading to ubuntu wily ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 5463 F pulseaudio /dev/snd/seq:timidity 10140 F timidity Date: Wed Apr 13 15:29:10 2016 DuplicateSignature: package:linux-image-4.2.0-35-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=7ff76835-7221-42f5-ade0-a3e31f3b9834 InstallationDate: Installed on 2012-11-28 (1232 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Acer TravelMate 4050 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=UUID=4be25730-2dd3-432b-8342-1f3bd4c07ecb 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: grub-pc 2.02~beta2-29ubuntu0.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-04-13 (0 days ago) dmi.bios.date: 08/10/2004 dmi.bios.vendor: ACER dmi.bios.version: V1.20 dmi.board.name: TravelMate 4050 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: temp dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnACER:bvrV1.20:bd08/10/2004:svnAcer:pnTravelMate4050:pvr290:rvnAcer:rnTravelMate4050:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 4050 dmi.product.version: 290 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs
** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567107 Title: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs Status in linux package in Ubuntu: Triaged Bug description: Because Generation 2 virtual machines in Hyper-V are presented with a minimal set of EFI hardware, the kernel module "hyperv_keyboard" must be present to interact with the console keyboard. On systems with disk encryption, the user will be prompted for the key to decrypt the disk, but cannot enter the password because no keyboard driver is present. This issue appears to exist in all Ubuntu releases that support EFI and are therefore eligible to be used as Generation 2 VMs, most recently tried with the April 5 ISO of the day for 16.04 (pre- release). This module *is* present when the grub menu is presented and later when the kernel is fully loaded. FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will also be needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570024] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: 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/1570024 Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: upgrading to ubuntu wily ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 5463 F pulseaudio /dev/snd/seq:timidity 10140 F timidity Date: Wed Apr 13 15:29:10 2016 DuplicateSignature: package:linux-image-4.2.0-35-generic:(not installed):subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=7ff76835-7221-42f5-ade0-a3e31f3b9834 InstallationDate: Installed on 2012-11-28 (1232 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Acer TravelMate 4050 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=UUID=4be25730-2dd3-432b-8342-1f3bd4c07ecb 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: grub-pc 2.02~beta2-29ubuntu0.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.2.0-35-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2016-04-13 (0 days ago) dmi.bios.date: 08/10/2004 dmi.bios.vendor: ACER dmi.bios.version: V1.20 dmi.board.name: TravelMate 4050 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: temp dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnACER:bvrV1.20:bd08/10/2004:svnAcer:pnTravelMate4050:pvr290:rvnAcer:rnTravelMate4050:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 4050 dmi.product.version: 290 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs
** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Package changed: linux (Ubuntu Xenial) => initramfs-tools (Ubuntu Xenial) ** Changed in: initramfs-tools (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567107 Title: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: In Progress Bug description: Because Generation 2 virtual machines in Hyper-V are presented with a minimal set of EFI hardware, the kernel module "hyperv_keyboard" must be present to interact with the console keyboard. On systems with disk encryption, the user will be prompted for the key to decrypt the disk, but cannot enter the password because no keyboard driver is present. This issue appears to exist in all Ubuntu releases that support EFI and are therefore eligible to be used as Generation 2 VMs, most recently tried with the April 5 ISO of the day for 16.04 (pre- release). This module *is* present when the grub menu is presented and later when the kernel is fully loaded. FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will also be needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
As noted, Xenial kernel is not supporting POWER7 cpu. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le Status in QEMU: Invalid Status in linux package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Bug description: qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image as part of the certification process. This on an IBM ppc64le in PowerVM mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no error output. ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio WARNING: Image format was not specified for 'seed.iso' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. SLOF ** QEMU Starting Build Date = Jan 29 2016 18:58:37 FW Version = buildd@ release 20151103 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/vty@7100 Populating /vdevice/nvram@7101 Populating /vdevice/l-lan@7102 Populating /vdevice/v-scsi@7103 SCSI: Looking for devices 8200 CD-ROM : "QEMU QEMU CD-ROM 2.5+" Populating /pci@8002000 00 1800 (D) : 1af4 1001virtio [ block ] 00 1000 (D) : 1af4 1001virtio [ block ] 00 0800 (D) : 106b 003fserial bus [ usb-ohci ] 00 (D) : 1234 qemu vga No NVRAM common partition, re-initializing... Installing QEMU fb Scanning USB OHCI: initializing USB Keyboard USB mouse No console specified using screen & keyboard Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@3 ... E3404: Not a bootable device! Trying to load: from: /pci@8002000/scsi@2 ... Successfully loaded Linux ppc64le #31-Ubuntu SMP F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-ppc 1:2.5+dfsg-5ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic ppc64le ApportVersion: 2.20-0ubuntu3 Architecture: ppc64el Date: Wed Mar 30 14:10:01 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 1172 2 0.0 [kvm-irqfd-clean] qemu-nbdSsl 0 0 13467 1 0.0 qemu-nbd -c /dev/nbd0 xenial-server-cloudimg-ppc64el-disk1.img qemu-system-ppc Sl+ 1000 1000 18973 18896 101 qemu-system-ppc64 -m 256 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-16-generic root=UUID=92d820c8-ab25-497b-9b1e-f1435992bbf3 ro ProcLoadAvg: 1.08 0.94 0.58 2/616 19571 ProcLocks: 1: POSIX ADVISORY WRITE 886 00:13:381 0 EOF 2: POSIX ADVISORY WRITE 1339 00:13:528 0 EOF 3: FLOCK ADVISORY WRITE 1284 00:13:522 0 EOF 4: POSIX ADVISORY WRITE 2281 00:13:563 0 EOF 5: POSIX ADVISORY WRITE 1331 00:13:536 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-16-generic (buildd@bos01-ppc64el-001) (gcc version 5.3.1 20160320 (Ubuntu/Linaro/IBM 5.3.1-12ubuntu4) ) #32-Ubuntu SMP Thu Mar 24 22:31:14 UTC 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) bootlist: /pci@8002011/pci1014,034A@0/sas/disk@4068402c40 /pci@8002018/ethernet@0:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/ethernet@0,1:speed=auto,duplex=auto,csarch,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 /pci@8002018/
[Kernel-packages] [Bug 1570054] [NEW] kernel BUG at /build/linux-lts-vivid-xAeXSD/linux-lts-vivid-3.19.0/kernel/smpboot.c:134!
Public bug reported: It has been observed a couple Ubuntu boots hang with the error: kernel BUG at /build/linux-lts-vivid-xAeXSD/linux-lts-vivid-3.19.0/kernel/smpboot.c:134! This is on Linux version 3.19.0-43-generic (buildd@lgw01-16) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #49~14.04.1-Ubuntu SMP Thu Dec 31 15:44:49 UTC 2015 (Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10) The fix for this bug is upstream commit 00df35f991914db6b8bde8cf09808e19a9cffc3d. That commit has be cc'd to stable. However, this fix is needed before the commit comes down via the normal stable update process. ** Affects: linux (Ubuntu) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-lts-vivid (Ubuntu) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Tags: kernel-key ** Also affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-vivid (Ubuntu) Status: New => In Progress ** Changed in: linux-lts-vivid (Ubuntu) Importance: Undecided => High ** Changed in: linux-lts-vivid (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570054 Title: kernel BUG at /build/linux-lts-vivid-xAeXSD/linux-lts- vivid-3.19.0/kernel/smpboot.c:134! Status in linux package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Bug description: It has been observed a couple Ubuntu boots hang with the error: kernel BUG at /build/linux-lts-vivid-xAeXSD/linux-lts-vivid-3.19.0/kernel/smpboot.c:134! This is on Linux version 3.19.0-43-generic (buildd@lgw01-16) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #49~14.04.1-Ubuntu SMP Thu Dec 31 15:44:49 UTC 2015 (Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10) The fix for this bug is upstream commit 00df35f991914db6b8bde8cf09808e19a9cffc3d. That commit has be cc'd to stable. However, this fix is needed before the commit comes down via the normal stable update process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569849] [NEW] Crash in intel_uncore.c:619
You have been subscribed to a public bug: The i915 driver crashed on Kubuntu 16.04 beta 2 on a Lenovo Thinkpad X1 3rd generation. I think the crash happened when KDE attempted to perform automatic login. After the crash, I believe X was restarted. The login screen was shown and I could log in and use the computer normally. [ 52.782406] [ cut here ] [ 52.782494] WARNING: CPU: 1 PID: 1009 at /build/linux-XwpX40/linux-4.4.0/drivers/gpu/drm/i915/intel_uncore.c:619 hsw_unclaimed_reg_debug+0x69/0x90 [i915]() [ 52.782501] Unclaimed register detected after reading register 0x223a0 [ 52.782503] Modules linked in: ctr ccm hid_logitech_hidpp hid_generic hid_microsoft hid_logitech_dj cdc_ether usbnet r8152 snd_usb_audio mii snd_usbmidi_lib usbhid hid uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media binfmt_misc arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iwlmvm irqbypass mac80211 input_leds joydev serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlwifi thinkpad_acpi snd_seq_midi nvram snd_seq_midi_event cfg80211 snd_hda_intel snd_hda_codec intel_pch_thermal lpc_ich snd_hda_core snd_rawmidi snd_hwdep mei_me snd_pcm snd_seq mei shpchp snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul [ 52.782597] aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt fb_sys_fops ptp libahci pps_core drm wmi video fjes [ 52.782629] CPU: 1 PID: 1009 Comm: Xorg Tainted: GW 4.4.0-18-generic #34-Ubuntu [ 52.782632] Hardware name: LENOVO 20BTS2YF00/20BTS2YF00, BIOS N14ET32W (1.10 ) 08/13/2015 [ 52.782635] 0086 980a8dd8 88024dc43cd8 813e9243 [ 52.782640] 88024dc43d20 c02b91c0 88024dc43d10 81080f62 [ 52.782643] 88023e98 000223a0 0102 000223a0 [ 52.782647] Call Trace: [ 52.782650][] dump_stack+0x63/0x90 [ 52.782673] [] warn_slowpath_common+0x82/0xc0 [ 52.782678] [] warn_slowpath_fmt+0x5c/0x80 [ 52.782739] [] hsw_unclaimed_reg_debug+0x69/0x90 [i915] [ 52.782790] [] gen6_read32+0xd1/0x1a0 [i915] [ 52.782839] [] intel_lrc_irq_handler+0x38/0x240 [i915] [ 52.782895] [] ? drm_handle_vblank+0x1ea/0x2b0 [drm] [ 52.782946] [] gen8_gt_irq_handler+0x217/0x240 [i915] [ 52.782987] [] gen8_irq_handler+0xa1/0x740 [i915] [ 52.782997] [] handle_irq_event_percpu+0x8d/0x1d0 [ 52.783002] [] handle_irq_event+0x3e/0x60 [ 52.783007] [] handle_edge_irq+0x7d/0x150 [ 52.783014] [] handle_irq+0x1a/0x30 [ 52.783021] [] do_IRQ+0x4b/0xd0 [ 52.783030] [] common_interrupt+0x82/0x82 [ 52.783032][] ? gen8_emit_request+0x224/0x320 [i915] [ 52.783116] [] __i915_add_request+0x147/0x210 [i915] [ 52.783157] [] i915_gem_execbuffer_retire_commands+0x26/0x30 [i915] [ 52.783197] [] intel_execlists_submission+0x2eb/0x410 [i915] [ 52.783228] [] i915_gem_do_execbuffer.isra.25+0xfa0/0x12a0 [i915] [ 52.783262] [] ? i915_gem_object_retire__write+0x51/0x90 [i915] [ 52.783295] [] i915_gem_execbuffer2+0xb2/0x240 [i915] [ 52.783322] [] ? i915_gem_busy_ioctl+0x92/0xe0 [i915] [ 52.783369] [] drm_ioctl+0x152/0x540 [drm] [ 52.783403] [] ? i915_gem_execbuffer+0x310/0x310 [i915] [ 52.783412] [] do_vfs_ioctl+0x29f/0x490 [ 52.783415] [] SyS_ioctl+0x79/0x90 [ 52.783423] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 52.783427] ---[ end trace 8b23540298125f35 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Apr 13 13:45:12 2016 DistUpgraded: 2016-04-13 13:29:17,470 DEBUG new topwidget None DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-08-20 (236 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150820) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: LENOVO 20BTS2YF00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0
[Kernel-packages] [Bug 1570061] Re: software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-g
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1570061 Title: software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream Status in linux-lts-vivid package in Ubuntu: New Bug description: Ran software updater and received the aforementioned error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-58-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 13 14:44:23 2016 DuplicateSignature: package:linux-image-3.19.0-58-generic:(not installed):cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2016-02-20 (52 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1570061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569429] [NEW] touchscreen not working
You have been subscribed to a public bug: In WIndows 10 the touch screen works. But in Ubuntu 16:04 it is not working. Although with 14:04 and 15:04 it worked earlier. But with 16:04 it doesn't work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 12 21:18:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80dd] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd] InstallationDate: Installed on 2016-02-21 (50 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd03/03/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 12 21:16:11 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- touchscreen not working https://bugs.launchpad.net/bugs/1569429 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 1570061] [NEW] software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58
Public bug reported: Ran software updater and received the aforementioned error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-58-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 13 14:44:23 2016 DuplicateSignature: package:linux-image-3.19.0-58-generic:(not installed):cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2016-02-20 (52 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1570061 Title: software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream Status in linux-lts-vivid package in Ubuntu: New Bug description: Ran software updater and received the aforementioned error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-58-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 13 14:44:23 2016 DuplicateSignature: package:linux-image-3.19.0-58-generic:(not installed):cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2016-02-20 (52 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1570061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569849] Re: Crash in intel_uncore.c:619
** Package changed: xorg (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/1569849 Title: Crash in intel_uncore.c:619 Status in linux package in Ubuntu: New Bug description: The i915 driver crashed on Kubuntu 16.04 beta 2 on a Lenovo Thinkpad X1 3rd generation. I think the crash happened when KDE attempted to perform automatic login. After the crash, I believe X was restarted. The login screen was shown and I could log in and use the computer normally. [ 52.782406] [ cut here ] [ 52.782494] WARNING: CPU: 1 PID: 1009 at /build/linux-XwpX40/linux-4.4.0/drivers/gpu/drm/i915/intel_uncore.c:619 hsw_unclaimed_reg_debug+0x69/0x90 [i915]() [ 52.782501] Unclaimed register detected after reading register 0x223a0 [ 52.782503] Modules linked in: ctr ccm hid_logitech_hidpp hid_generic hid_microsoft hid_logitech_dj cdc_ether usbnet r8152 snd_usb_audio mii snd_usbmidi_lib usbhid hid uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media binfmt_misc arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iwlmvm irqbypass mac80211 input_leds joydev serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlwifi thinkpad_acpi snd_seq_midi nvram snd_seq_midi_event cfg80211 snd_hda_intel snd_hda_codec intel_pch_thermal lpc_ich snd_hda_core snd_rawmidi snd_hwdep mei_me snd_pcm snd_seq mei shpchp snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul [ 52.782597] aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt fb_sys_fops ptp libahci pps_core drm wmi video fjes [ 52.782629] CPU: 1 PID: 1009 Comm: Xorg Tainted: GW 4.4.0-18-generic #34-Ubuntu [ 52.782632] Hardware name: LENOVO 20BTS2YF00/20BTS2YF00, BIOS N14ET32W (1.10 ) 08/13/2015 [ 52.782635] 0086 980a8dd8 88024dc43cd8 813e9243 [ 52.782640] 88024dc43d20 c02b91c0 88024dc43d10 81080f62 [ 52.782643] 88023e98 000223a0 0102 000223a0 [ 52.782647] Call Trace: [ 52.782650][] dump_stack+0x63/0x90 [ 52.782673] [] warn_slowpath_common+0x82/0xc0 [ 52.782678] [] warn_slowpath_fmt+0x5c/0x80 [ 52.782739] [] hsw_unclaimed_reg_debug+0x69/0x90 [i915] [ 52.782790] [] gen6_read32+0xd1/0x1a0 [i915] [ 52.782839] [] intel_lrc_irq_handler+0x38/0x240 [i915] [ 52.782895] [] ? drm_handle_vblank+0x1ea/0x2b0 [drm] [ 52.782946] [] gen8_gt_irq_handler+0x217/0x240 [i915] [ 52.782987] [] gen8_irq_handler+0xa1/0x740 [i915] [ 52.782997] [] handle_irq_event_percpu+0x8d/0x1d0 [ 52.783002] [] handle_irq_event+0x3e/0x60 [ 52.783007] [] handle_edge_irq+0x7d/0x150 [ 52.783014] [] handle_irq+0x1a/0x30 [ 52.783021] [] do_IRQ+0x4b/0xd0 [ 52.783030] [] common_interrupt+0x82/0x82 [ 52.783032][] ? gen8_emit_request+0x224/0x320 [i915] [ 52.783116] [] __i915_add_request+0x147/0x210 [i915] [ 52.783157] [] i915_gem_execbuffer_retire_commands+0x26/0x30 [i915] [ 52.783197] [] intel_execlists_submission+0x2eb/0x410 [i915] [ 52.783228] [] i915_gem_do_execbuffer.isra.25+0xfa0/0x12a0 [i915] [ 52.783262] [] ? i915_gem_object_retire__write+0x51/0x90 [i915] [ 52.783295] [] i915_gem_execbuffer2+0xb2/0x240 [i915] [ 52.783322] [] ? i915_gem_busy_ioctl+0x92/0xe0 [i915] [ 52.783369] [] drm_ioctl+0x152/0x540 [drm] [ 52.783403] [] ? i915_gem_execbuffer+0x310/0x310 [i915] [ 52.783412] [] do_vfs_ioctl+0x29f/0x490 [ 52.783415] [] SyS_ioctl+0x79/0x90 [ 52.783423] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 52.783427] ---[ end trace 8b23540298125f35 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Apr 13 13:45:12 2016 DistUpgraded: 2016-04-13 13:29:17,470 DEBUG new topwidget None DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-08-20 (236 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150820) JournalErrors: Error: command [
[Kernel-packages] [Bug 1569429] Re: touchscreen not working
try bisecting with mainline kernel builds, 15.04 had 3.19 so it regressed between it and 4.4. http://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1569429 Title: touchscreen not working Status in linux package in Ubuntu: Incomplete Bug description: In WIndows 10 the touch screen works. But in Ubuntu 16:04 it is not working. Although with 14:04 and 15:04 it worked earlier. But with 16:04 it doesn't work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 12 21:18:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80dd] Subsystem: Hewlett-Packard Company GM107M [GeForce GTX 950M] [103c:80dd] InstallationDate: Installed on 2016-02-21 (50 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160214) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b50c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP ENVY Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=00a78db6-4e85-4827-a204-386b28d7f737 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DD dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd03/03/2016:svnHewlett-Packard:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80DD:rvr64.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 12 21:16:11 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Unknown chipset: NV117 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1569849] 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/1569849 Title: Crash in intel_uncore.c:619 Status in linux package in Ubuntu: Confirmed Bug description: The i915 driver crashed on Kubuntu 16.04 beta 2 on a Lenovo Thinkpad X1 3rd generation. I think the crash happened when KDE attempted to perform automatic login. After the crash, I believe X was restarted. The login screen was shown and I could log in and use the computer normally. [ 52.782406] [ cut here ] [ 52.782494] WARNING: CPU: 1 PID: 1009 at /build/linux-XwpX40/linux-4.4.0/drivers/gpu/drm/i915/intel_uncore.c:619 hsw_unclaimed_reg_debug+0x69/0x90 [i915]() [ 52.782501] Unclaimed register detected after reading register 0x223a0 [ 52.782503] Modules linked in: ctr ccm hid_logitech_hidpp hid_generic hid_microsoft hid_logitech_dj cdc_ether usbnet r8152 snd_usb_audio mii snd_usbmidi_lib usbhid hid uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media binfmt_misc arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iwlmvm irqbypass mac80211 input_leds joydev serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlwifi thinkpad_acpi snd_seq_midi nvram snd_seq_midi_event cfg80211 snd_hda_intel snd_hda_codec intel_pch_thermal lpc_ich snd_hda_core snd_rawmidi snd_hwdep mei_me snd_pcm snd_seq mei shpchp snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul [ 52.782597] aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt fb_sys_fops ptp libahci pps_core drm wmi video fjes [ 52.782629] CPU: 1 PID: 1009 Comm: Xorg Tainted: GW 4.4.0-18-generic #34-Ubuntu [ 52.782632] Hardware name: LENOVO 20BTS2YF00/20BTS2YF00, BIOS N14ET32W (1.10 ) 08/13/2015 [ 52.782635] 0086 980a8dd8 88024dc43cd8 813e9243 [ 52.782640] 88024dc43d20 c02b91c0 88024dc43d10 81080f62 [ 52.782643] 88023e98 000223a0 0102 000223a0 [ 52.782647] Call Trace: [ 52.782650][] dump_stack+0x63/0x90 [ 52.782673] [] warn_slowpath_common+0x82/0xc0 [ 52.782678] [] warn_slowpath_fmt+0x5c/0x80 [ 52.782739] [] hsw_unclaimed_reg_debug+0x69/0x90 [i915] [ 52.782790] [] gen6_read32+0xd1/0x1a0 [i915] [ 52.782839] [] intel_lrc_irq_handler+0x38/0x240 [i915] [ 52.782895] [] ? drm_handle_vblank+0x1ea/0x2b0 [drm] [ 52.782946] [] gen8_gt_irq_handler+0x217/0x240 [i915] [ 52.782987] [] gen8_irq_handler+0xa1/0x740 [i915] [ 52.782997] [] handle_irq_event_percpu+0x8d/0x1d0 [ 52.783002] [] handle_irq_event+0x3e/0x60 [ 52.783007] [] handle_edge_irq+0x7d/0x150 [ 52.783014] [] handle_irq+0x1a/0x30 [ 52.783021] [] do_IRQ+0x4b/0xd0 [ 52.783030] [] common_interrupt+0x82/0x82 [ 52.783032][] ? gen8_emit_request+0x224/0x320 [i915] [ 52.783116] [] __i915_add_request+0x147/0x210 [i915] [ 52.783157] [] i915_gem_execbuffer_retire_commands+0x26/0x30 [i915] [ 52.783197] [] intel_execlists_submission+0x2eb/0x410 [i915] [ 52.783228] [] i915_gem_do_execbuffer.isra.25+0xfa0/0x12a0 [i915] [ 52.783262] [] ? i915_gem_object_retire__write+0x51/0x90 [i915] [ 52.783295] [] i915_gem_execbuffer2+0xb2/0x240 [i915] [ 52.783322] [] ? i915_gem_busy_ioctl+0x92/0xe0 [i915] [ 52.783369] [] drm_ioctl+0x152/0x540 [drm] [ 52.783403] [] ? i915_gem_execbuffer+0x310/0x310 [i915] [ 52.783412] [] do_vfs_ioctl+0x29f/0x490 [ 52.783415] [] SyS_ioctl+0x79/0x90 [ 52.783423] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 52.783427] ---[ end trace 8b23540298125f35 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Apr 13 13:45:12 2016 DistUpgraded: 2016-04-13 13:29:17,470 DEBUG new topwidget None DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-08-20 (236 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64
[Kernel-packages] [Bug 1563485] Comment bridged from LTC Bugzilla
--- Comment From mro...@us.ibm.com 2016-04-13 15:22 EDT--- Canonical FYI: Commit 6f21dbca4c985279200866b7f50b1f26b014c27a (UBUNTU: SAUCE: (noup) cxlflash: Move to exponential back-off when cmd_room is not available) is now upstream (ea76543127da32dec28af0a13ea1b06625fc085e). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563485 Title: cxlflash: Backport upstream cxlflash commits and submitting a noup patch to Xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Canonical, We would like to ask to include three patches to Ubuntu 16.04 in order to fix some cxlflash bugs and performance issues. They are: 1. http://marc.info/?l=linux-scsi&m=145893415107594&w=2 (not upstream yet) 2. 83430833b4d4a9c9b23964babbeb1f36450f8136 3. 603ecce95f4817074a724a889cd88c3c8210f933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1514066] Re: Touchpad not working on ASUS ZenBook UX305CA-FC037T
Works for me with kernel 4.5.0-040500-generic in Mint 17.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1514066 Title: Touchpad not working on ASUS ZenBook UX305CA-FC037T Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Touchpad is not working on a new installation of ubuntu 15.10 HW is ok; was tested on W10. Same issue as described here: http://askubuntu.com/questions/693701/touchpad-not-workingon-asus-ux305-under-ubuntu-15-10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-17-generic 4.2.0-17.21 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmp1724 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 7 13:29:42 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=38e264e5-e90e-4b33-a8a3-302a4327fe70 InstallationDate: Installed on 2015-11-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 004: ID 046d:c06c Logitech, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305CA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic.efi.signed root=UUID=3d3973ea-7464-4c42-8e63-e7d3f13cf052 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-17-generic N/A linux-backports-modules-4.2.0-17-generic N/A linux-firmware1.149.1 SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305CA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305CA 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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1514066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
On NUC NUC5i3RYB (Lubuntu 15.10 amd64) BIOS : RYBDWi35.86A.0354.2016.0120.0912 Date: 01/20/2016 kernel 4.6.0-040600rc3-generic from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.6-rc3-wily/ Finally fixed this for me (Yamaha RX-V475 hdmi handling was/is still buggy). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On a recent intel NUC using i915 graphics, I get the following errors in dmesg: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! There are two monitors connected to this box, one with mini- HDMI->HDMI, one with mini-DP->HDMI cable. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=80896 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.26.25 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 10:07:31 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 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/linux/+bug/1488719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570061] Re: software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-g
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1570061 Title: software upgrade failed - package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream Status in linux-lts-vivid package in Ubuntu: Invalid Bug description: Ran software updater and received the aforementioned error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-58-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-56.62~14.04.1-generic 3.19.8-ckt15 Uname: Linux 3.19.0-56-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Wed Apr 13 14:44:23 2016 DuplicateSignature: package:linux-image-3.19.0-58-generic:(not installed):cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2016-02-20 (52 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.12 SourcePackage: linux-lts-vivid Title: package linux-image-3.19.0-58-generic (not installed) failed to install/upgrade: cannot copy extracted data for './lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko' to '/lib/modules/3.19.0-58-generic/kernel/fs/ceph/ceph.ko.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1570061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
My Aquarius E5 will connect via Bluetooth to my VW system, but fails to make calls. This problem was not there prior to OTA 8.5. I'd had hoped that this problem would have been resolved by OTA-10. The problem has got worse for my handset. It will connect fine, but when making call, the Bluetooth will be discount and connection become difficult if the phone does not get rebooted. The problem I think for me, lays with the phone's ability to use the car's system as a loud speaker. The call does connect but I cannot hear the recipient, nor can they hear me. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
Hi Joseph, Any updates on the bisect? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561389] Re: CVE-2016-0821
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561389 Title: CVE-2016-0821 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta sour
[Kernel-packages] [Bug 1561410] Re: CVE-2016-2185
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Description changed: Kernel panic on invalid USB device descriptor (ati_remote2 driver) + + Break-Fix: - 950336ba3e4a1ffd2ca60d29f6ef386dd2c7351d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561410 Title: CVE-2016-2185 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New St
[Kernel-packages] [Bug 1561409] Re: CVE-2016-2184
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561409 Title: CVE-2016-2184 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: New Status in linux-armadaxp source package in Xenial
[Kernel-packages] [Bug 1561399] Re: CVE-2016-0823
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Released ** Changed in: linux-lts-xenial (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561399 Title: CVE-2016-0823 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Invalid Status in linux-armadaxp source package i
[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
I am attaching the log with OTA10.1. As far as I can tell, the error is still the same. But all the experience I have with debugging bluetooth errors is what you see in this bug report. ** Attachment added: "Syslog with verbose bluetooth after OTA10.1" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+attachment/4636161/+files/syslog_OTA10.1.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563485] Re: cxlflash: Backport upstream cxlflash commits and submitting a noup patch to Xenial
The upstream commit appears to be identical, so I'll just leave well enough alone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563485 Title: cxlflash: Backport upstream cxlflash commits and submitting a noup patch to Xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Canonical, We would like to ask to include three patches to Ubuntu 16.04 in order to fix some cxlflash bugs and performance issues. They are: 1. http://marc.info/?l=linux-scsi&m=145893415107594&w=2 (not upstream yet) 2. 83430833b4d4a9c9b23964babbeb1f36450f8136 3. 603ecce95f4817074a724a889cd88c3c8210f933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561414] Re: CVE-2016-2188
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561414 Title: CVE-2016-2188 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: New Status in linux-armadaxp source package in Xenial
[Kernel-packages] [Bug 1561411] Re: CVE-2016-2186
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561411 Title: CVE-2016-2186 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: New Status in linux-armadaxp source package in Xenial
[Kernel-packages] [Bug 1549494] Re: arm64: guest hangs when ntpd is running
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549494 Title: arm64: guest hangs when ntpd is running Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: Impact: KVM guests hang on arm64 host running ntpd Fix: From linux-next: commit 1c5631c73fc2261a5df64a72c155cb53dcdc0c45 Author: Marc Zyngier Date: Wed Apr 6 09:37:22 2016 +0100 KVM: arm/arm64: Handle forward time correction gracefully BugLink: http://bugs.launchpad.net/bugs/1549494 On a host that runs NTP, corrections can have a direct impact on the background timer that we program on the behalf of a vcpu. In particular, NTP performing a forward correction will result in a timer expiring sooner than expected from a guest point of view. Not a big deal, we kick the vcpu anyway. But on wake-up, the vcpu thread is going to perform a check to find out whether or not it should block. And at that point, the timer check is going to say "timer has not expired yet, go back to sleep". This results in the timer event being lost forever. There are multiple ways to handle this. One would be record that the timer has expired and let kvm_cpu_has_pending_timer return true in that case, but that would be fairly invasive. Another is to check for the "short sleep" condition in the hrtimer callback, and restart the timer for the remaining time when the condition is detected. This patch implements the latter, with a bit of refactoring in order to avoid too much code duplication. Testcase: A) Install ntp on the host (I'm using a 2 socket ThunderX) B) Boot up a large VM (95 CPUs/4G memory) C) Within the VM, rebuild the Ubuntu kernel package If it doesn't hang - bug is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567581] image tools
--- Comment (attachment only) From bren...@br.ibm.com 2016-04-13 17:45 EDT--- ** Attachment added: "image tools" https://bugs.launchpad.net/bugs/1567581/+attachment/4636199/+files/linux-tools-4.4.0-18breno-generic_4.4.0-18breno_ppc64el.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1567581 Title: Surelock GA2 SP1: surelock02p05: Not seeing sgX devices for LUNs after upgrading to Ubuntu 16.04 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Not seeing sgX device for LUNs after upgrading to Ubuntu 16.04 -17 kernel This is probably caused by the following patch added on Ubuntu kernel 4.4.0-17: - SAUCE: (noup) powerpc/pci: Assign fixed PHB number based on device-tree properties". That said, i would like to ask Canonical to revert the SAUCE patch 42a1e725ec14f0ce4d5e5b0fcf6d23260d0dcc08. It has a bad side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1567581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
Following a suggestion from jbmacbrodie to minimise the blueman device
manager after pairing, I tried again. This time, I used the command-line
bluetoothctl program as sudo: the "paired-devices" command showed the
device was already paired from my previous session. "info [mac addr]"
showed it was not legacy-paired and not currently connected.
I flicked the switch on the docking unit (a bluetooth keyboard with
touchpad) so it would try to establish a connection. I then issued the
"connect [mac addr]", and bluetoothctl briefly showed it was connected
and the blue LED on the keyboard changed from blinking, to solid on,
then back to solid off in a matter of a few seconds.
syslog showed:
Apr 8 15:28:39 Muscat bluetoothd[610]: Can't get HIDP connection info
Apr 8 15:28:40 Muscat kernel: [ 1066.735075] hid-generic 0005:0B05:8502.0004:
unknown main item tag 0x0
Apr 8 15:28:40 Muscat kernel: [ 1066.735354] input: ASUS T300CHI DOCKING as
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0004/input/input16
Apr 8 15:28:40 Muscat kernel: [ 1066.735950] hid-generic 0005:0B05:8502.0004:
input,hidraw3: BLUETOOTH HID v0.01 Keyboard [ASUS T300CHI DOCKING] on
60:57:18:59:0a:64
Apr 8 15:28:40 Muscat bluetoothd[610]: No agent available for request type 0
Apr 8 15:28:40 Muscat bluetoothd[610]: device_request_pin: Operation not
permitted
I had just rebooted the latest (4.4.0-17-generic) kernel and bluetoothd
logged the "not enough handles" message again when starting. I don't
know whether this is a symptom of the kernel bug, or something
completely different!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10: bluetoothd reports "Not enough handles to register service" at
start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
Yes, the bisect ended in a really strange results. I reported this commit as the cause: commit c01fac1c77a00227f706a1654317023e3f4ac7f0 Author: Felix Fietkau Date: Wed Jul 23 15:40:54 2014 +0200 ath9k: fix aggregation session lockup I'm not really sure how a wireless driver could cause this. Even stranger is I build a 3.13.0-35 kernel with this commit reverted, and I'm unable to reproduce the bug. If anyone else wants to test that kernel, it can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1470250/trusty-revert/3.13.0-35/ I'm now testing Wily and Xenial kernels with the commit reverted as well to ensure a revert fixes those kernels as well. If anyone else wants to test those kernels, then can be downloaded from: Trusty: http://kernel.ubuntu.com/~jsalisbury/lp1470250/trusty-revert/ WIly: http://kernel.ubuntu.com/~jsalisbury/lp1470250/wily-revert/ Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1470250/xenial-revert/ If that commit is indeed the cause of the bug, we should do some more investigation to understand what is happening. I'll post my testing results of the other kernels within two days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] [NEW] [Hyper-V] In-flight PCI Passthrough Patches
Public bug reported: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 56 drivershv Record MMIO range in use by frame buffer.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636243/+files/PATCH%20v5%2056%20drivershv%20Record%20MMIO%20range%20in%20use%20by%20frame%20buffer.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
Additional comment for 1/6 ** Attachment added: "PATCH v5 16 drivershv Lock access to hyperv_mmio resource tree (2).msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636246/+files/PATCH%20v5%2016%20drivershv%20Lock%20access%20to%20hyperv_mmio%20resource%20tree%20%282%29.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
Additional comment for 1/6 ** Attachment added: "PATCH v5 16 drivershv Lock access to hyperv_mmio resource tree (1).msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636245/+files/PATCH%20v5%2016%20drivershv%20Lock%20access%20to%20hyperv_mmio%20resource%20tree%20%281%29.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 46 drivershv Track allocations of children of hv_vmbus in private resource tree.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636242/+files/PATCH%20v5%2046%20drivershv%20Track%20allocations%20of%20children%20of%20hv_vmbus%20in%20private%20resource%20tree.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 26 drivershv Call vmbus_mmio_free() to reverse vmbus_mmio_allocate().msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636239/+files/PATCH%20v5%2026%20drivershv%20Call%20vmbus_mmio_free%28%29%20to%20reverse%20vmbus_mmio_allocate%28%29.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
Additional comment for 1/6 ** Attachment added: "PATCH v5 16 drivershv Lock access to hyperv_mmio resource tree (3).msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636247/+files/PATCH%20v5%2016%20drivershv%20Lock%20access%20to%20hyperv_mmio%20resource%20tree%20%283%29.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 36 drivershv Reverse order of resources in hyperv_mmio.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636241/+files/PATCH%20v5%2036%20drivershv%20Reverse%20order%20of%20resources%20in%20hyperv_mmio.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 66 drivershv Separate out frame buffer logic when picking MMIO range.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636244/+files/PATCH%20v5%2066%20drivershv%20Separate%20out%20frame%20buffer%20logic%20when%20picking%20MMIO%20range.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start
I also true using an old bluetooth usb dongle. I used it on the asus
T300, but that made no difference. I also tried it on my dell 1558
laptop, with 16.04 (64-bit) and 15.10 (32-bit with bluez 5.35). The
16.04 test was basically the same as on the asus. The 15.10 test was
different in detail, but still showed the docking station briefly
connecting, but disconnecting a second or so later.
All tests produced the "not enough handles" message from bluetoothd. Is
anyone successfully using bluetooth with these later ubuntu kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10: bluetoothd reports "Not enough handles to register service" at
start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 16 drivershv Lock access to hyperv_mmio resource tree.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636238/+files/PATCH%20v5%2016%20drivershv%20Lock%20access%20to%20hyperv_mmio%20resource%20tree.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1556880] Re: CVE-2016-3138
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1556880 Title: CVE-2016-3138 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: New Status in linux-armadaxp source package in Xenial
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Attachment added: "PATCH v5 06 drivershv Ensure that bridge windows don't overlap.msg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+attachment/4636237/+files/PATCH%20v5%2006%20drivershv%20Ensure%20that%20bridge%20windows%20don%27t%20overlap.msg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: New Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1558847] Re: CVE-2016-3156
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1558847 Title: CVE-2016-3156 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: New Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-gold
[Kernel-packages] [Bug 1554260] Re: CVE-2016-2847
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1554260 Title: CVE-2016-2847 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: Fix Released Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-armadaxp source package in Xenia
[Kernel-packages] [Bug 1570124] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1570124 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/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: Incomplete Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561388] Re: CVE-2016-3157
** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Description changed: [I/O port access privilege escalation in x86-64 Linux] - Break-Fix: - - + Break-Fix: - b7a584598aea7ca73140cb87b40319944dd3393f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1561388 Title: CVE-2016-3157 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: N
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
I'm also going to try reverting this commit on a 4.2.0-27 kernel that I was able to see this issue on; and see if I can repro it there as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567539] Re: Failure to dump with trusty+3.16 on ppc64el
So it looks like this crashkernel argument is not resulting in any reserved memory. The correct crashkernel argument should look like this. crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M Additionally my earlier failures here were the result of no reserved memory being allocated due to the way crashkernel parses the @32M. So to recap, you definitely need the @32M. And there seems to be a parsing issue if multiple @##M offsets are desired. -- 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/1567539 Title: Failure to dump with trusty+3.16 on ppc64el Status in makedumpfile package in Ubuntu: Confirmed Bug description: Test case # sudo apt-get install linux-crashdump set USE_KDUMP=1 in /etc/default/kdump-tools # sudo shutdown -r now echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger It looks like there was insufficient memory devoted to the crash kernel. The defaults were used, and the kernel had 256G of ram, and only 2.6G were in use at the time of inducing the crash. Console log [ 290.509423] SysRq : Trigger a crash [ 290.509526] Unable to handle kernel paging request for data at address 0x [ 290.509606] Faulting instruction address: 0xc05d9c94 [ 290.509672] Oops: Kernel access of bad area, sig: 11 [#1] [ 290.509723] SMP NR_CPUS=2048 NUMA PowerNV [ 290.509776] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt rtc_generic i2c_opal powernv_rng uio_pdrv_genirq ipmi_powernv ipmi_msghandler uio mlx4_en vxlan ses enclosure mlx4_core ipr [ 290.510178] CPU: 121 PID: 2976 Comm: tee Not tainted 3.16.0-69-generic #89~14.04.1-Ubuntu [ 290.510254] task: c01fdccf4a80 ti: c01fdcd58000 task.ti: c01fdcd58000 [ 290.510330] NIP: c05d9c94 LR: c05dad0c CTR: c05d9c60 [ 290.510406] REGS: c01fdcd5b9d0 TRAP: 0300 Not tainted (3.16.0-69-generic) [ 290.510480] MSR: 90009033 CR: 28004024 XER: 2000 [ 290.510671] CFAR: c0009368 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05dad0c c01fdcd5bc50 c13d7d00 0063 GPR04: c6548540 c6558da8 00016fa0 c1596218 GPR08: c0e37d00 0001 00016fa0 GPR12: c05d9c60 c7bc4100 GPR16: GPR20: 100094d8 100094c0 GPR24: 0001 100094d8 0004 GPR28: c130f6c0 0063 c12ed7a0 c130fa80 [ 290.511676] NIP [c05d9c94] sysrq_handle_crash+0x34/0x50 [ 290.511742] LR [c05dad0c] __handle_sysrq+0xec/0x280 [ 290.511793] Call Trace: [ 290.511820] [c01fdcd5bc50] [c01fdcd5bcb0] 0xc01fdcd5bcb0 (unreliable) [ 290.511911] [c01fdcd5bc70] [c05dad0c] __handle_sysrq+0xec/0x280 [ 290.511988] [c01fdcd5bd10] [c05db4dc] write_sysrq_trigger+0x7c/0xa0 [ 290.512078] [c01fdcd5bd40] [c032e1d0] proc_reg_write+0xb0/0x110 [ 290.512155] [c01fdcd5bd90] [c02a47ec] vfs_write+0xdc/0x260 [ 290.512231] [c01fdcd5bde0] [c02a558c] SyS_write+0x6c/0x110 [ 290.512308] [c01fdcd5be30] [c000a1d8] system_call+0x38/0xd0 [ 290.512383] Instruction dump: [ 290.512421] 3842e0a0 7c0802a6 f8010010 f821ffe1 6000 6000 3d42001b 392a006c [ 290.512546] 3941 9149 7c0004ac 3920 <9949> 38210020 e8010010 7c0803a6 [ 290.512674] ---[ end trace ba4afa55b8a163cd ]--- [ 290.512735] [ 290.513754] Sending IPI to other CPUs [ 290.514897] IPI complete [0.00] OPAL V3 detected ! [0.00] Using PowerNV machine description [0.00] Page sizes from device-tree: [0.00] base_shift=12: shift=12, sllp=0x, avpnm=0x, tlbiel=1, penc=0 [0.00] base_shift=12: shift=16, sllp=0x, avpnm=0x, tlbiel=1, penc=7 [0.00] base_shift=12: shift=24, sllp=0x, avpnm=0x, tlbiel=1, penc=56 [0.00] base_shift=16: shift=16, sllp=0x0110, avpnm=0x, tlbiel=1, penc=1 [0.00] base_shift=16: shift=24, sllp=0x0110, avpnm=0x, tlbiel=1, penc=8 [0.00] base_shift=24: shift=24, sllp=0x0100, avpnm=0x0001, tlbiel=0, penc=0 [0.00] base_shift=34: shift=34, sllp=0x0120, avpnm=0x07ff, tlbiel=0, penc=3 [0.00] Using 1TB segments [0.00] kvm_cma: CMA: failed to reserve 128 MiB [0.00] Found initrd at 0xc973:0xcafd9bd6 [0.
[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)
This has annoyed me through the years on different machines and on different distributions ((K)Ubuntu and Debian). I am here because I experienced it, once more, a few minutes ago. Hard-drive (SSDs are silent, but I could tell from the led) usage skyrocketed even though I do not have any swap partition. Mouse cursor lagged, and even Ctrl+Alt+F1 (take me to a console) or Ctrl+Alt+Backspace (terminate X) did not work. I had to hit the power button. If I can be of any help, I will do my best. This bug is the single worst thing in the Linux experience that I have ever had. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555351 Title: High load freezes ubuntu completely everytime (have to reboot) Status in linux package in Ubuntu: Incomplete Bug description: Whenever an intensive application runs which consumes lots of memory or hard drive i/o, Ubuntu freezes completely. It is even impossible to kill the offending task. Only "solution" is then to wait for the application to finish, or restart PC. Windows doesn't have this issue as bad as Ubuntu, in that Windows is always somewhat responsive, and you can attempt to kill the intensive application to recover the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-32-generic 4.2.0-32.37 ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 Uname: Linux 4.2.0-32-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/18210/fd/20: Input/output error USERPID ACCESS COMMAND /dev/snd/controlC0: cossio 2082 F pulseaudio /dev/snd/controlC1: cossio 2082 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 9 22:28:53 2016 HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac InstallationDate: Installed on 2015-08-03 (219 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: ASUSTeK COMPUTER INC. X550LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA 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.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage
This has annoyed me through the years on different machines and on different distributions ((K)Ubuntu and Debian). I am here because I experienced it, once more, a few minutes ago. Hard-drive (SSDs are silent, but I could tell from the led) usage skyrocketed even though I do not have any swap partition. Mouse cursor lagged, and even Ctrl+Alt+F1 (take me to a console) or Ctrl+Alt+Backspace (terminate X) did not work. I had to hit the power button. If I can be of any help, I will do my best. This bug is the single worst thing in the Linux experience that I have ever had. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1567539] Re: Failure to dump with trusty+3.16 on ppc64el
On 13.04.2016 [23:44:39 -], Dave Chiluk wrote: > So it looks like this crashkernel argument is not resulting in any reserved > memory. > The correct crashkernel argument should look like this. > crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M > > Additionally my earlier failures here were the result of no reserved > memory being allocated due to the way crashkernel parses the @32M. Totally my fault, I glossed that on reading, there is only one offset allowed, aiui, as only one of the above cases ever applies to a given execution. And the offset should not need to be different for differnt values (as the pre-allocated memory you are presumably bumping into is at the same location in all cases). -- 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/1567539 Title: Failure to dump with trusty+3.16 on ppc64el Status in makedumpfile package in Ubuntu: Confirmed Bug description: Test case # sudo apt-get install linux-crashdump set USE_KDUMP=1 in /etc/default/kdump-tools # sudo shutdown -r now echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger It looks like there was insufficient memory devoted to the crash kernel. The defaults were used, and the kernel had 256G of ram, and only 2.6G were in use at the time of inducing the crash. Console log [ 290.509423] SysRq : Trigger a crash [ 290.509526] Unable to handle kernel paging request for data at address 0x [ 290.509606] Faulting instruction address: 0xc05d9c94 [ 290.509672] Oops: Kernel access of bad area, sig: 11 [#1] [ 290.509723] SMP NR_CPUS=2048 NUMA PowerNV [ 290.509776] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt rtc_generic i2c_opal powernv_rng uio_pdrv_genirq ipmi_powernv ipmi_msghandler uio mlx4_en vxlan ses enclosure mlx4_core ipr [ 290.510178] CPU: 121 PID: 2976 Comm: tee Not tainted 3.16.0-69-generic #89~14.04.1-Ubuntu [ 290.510254] task: c01fdccf4a80 ti: c01fdcd58000 task.ti: c01fdcd58000 [ 290.510330] NIP: c05d9c94 LR: c05dad0c CTR: c05d9c60 [ 290.510406] REGS: c01fdcd5b9d0 TRAP: 0300 Not tainted (3.16.0-69-generic) [ 290.510480] MSR: 90009033 CR: 28004024 XER: 2000 [ 290.510671] CFAR: c0009368 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05dad0c c01fdcd5bc50 c13d7d00 0063 GPR04: c6548540 c6558da8 00016fa0 c1596218 GPR08: c0e37d00 0001 00016fa0 GPR12: c05d9c60 c7bc4100 GPR16: GPR20: 100094d8 100094c0 GPR24: 0001 100094d8 0004 GPR28: c130f6c0 0063 c12ed7a0 c130fa80 [ 290.511676] NIP [c05d9c94] sysrq_handle_crash+0x34/0x50 [ 290.511742] LR [c05dad0c] __handle_sysrq+0xec/0x280 [ 290.511793] Call Trace: [ 290.511820] [c01fdcd5bc50] [c01fdcd5bcb0] 0xc01fdcd5bcb0 (unreliable) [ 290.511911] [c01fdcd5bc70] [c05dad0c] __handle_sysrq+0xec/0x280 [ 290.511988] [c01fdcd5bd10] [c05db4dc] write_sysrq_trigger+0x7c/0xa0 [ 290.512078] [c01fdcd5bd40] [c032e1d0] proc_reg_write+0xb0/0x110 [ 290.512155] [c01fdcd5bd90] [c02a47ec] vfs_write+0xdc/0x260 [ 290.512231] [c01fdcd5bde0] [c02a558c] SyS_write+0x6c/0x110 [ 290.512308] [c01fdcd5be30] [c000a1d8] system_call+0x38/0xd0 [ 290.512383] Instruction dump: [ 290.512421] 3842e0a0 7c0802a6 f8010010 f821ffe1 6000 6000 3d42001b 392a006c [ 290.512546] 3941 9149 7c0004ac 3920 <9949> 38210020 e8010010 7c0803a6 [ 290.512674] ---[ end trace ba4afa55b8a163cd ]--- [ 290.512735] [ 290.513754] Sending IPI to other CPUs [ 290.514897] IPI complete [0.00] OPAL V3 detected ! [0.00] Using PowerNV machine description [0.00] Page sizes from device-tree: [0.00] base_shift=12: shift=12, sllp=0x, avpnm=0x, tlbiel=1, penc=0 [0.00] base_shift=12: shift=16, sllp=0x, avpnm=0x, tlbiel=1, penc=7 [0.00] base_shift=12: shift=24, sllp=0x, avpnm=0x, tlbiel=1, penc=56 [0.00] base_shift=16: shift=16, sllp=0x0110, avpnm=0x, tlbiel=1, penc=1 [0.00] base_shift=16: shift=24, sllp=0x0110, avpnm=0x, tlbiel=1, penc=8 [0.00] base_shift=24: shift=24, sllp=0x0100, avpnm=0x0001, tlbiel=0, penc=0
[Kernel-packages] [Bug 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
Patchset, no logs. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: Confirmed Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566828] Re: Suspension does not work, freezes the pc
Same problem, also on a Dell 7520. Suspend worked every ubuntu release up through 15.10, now the fan spins and never fully sleeps and can't be woken up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc Status in linux package in Ubuntu: Confirmed Bug description: I have this notebook HP 15 ac 191 nl Intel® Core™ i5-5200U with integrated Intel HD 5500 RAM 8 gb DEdicated GPU AMD Radeon R5 M330 I am running kubuntu 16.04 beta2. When i suspend the pc, gettin down the screen or givin the command in the menù, the screen goes black but the fan keeps running. So you can hear the fan working..and the pc got hot. It is also impossible to wake up the pc, it stays freezed in this condition, i have to force the shutdown with the power button pressing it for 3 sec. The problem is present every time i try to suspend the pc. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd01/18/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C2:rvr96.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1315 F pulseaudio /dev/snd/pcmC1D0c: ale1315 F...m pulseaudio /dev/snd/pcmC1D0p: ale1315 F...m pulseaudio /dev/snd/controlC1: ale1315 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0c420aef-5eec-47f9-90cc-94eae92e8388 InstallationDate: Installed on 2016-03-31 (5 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-16-generic.efi.signed root=UUID=623bb030-402f-4ae0-b47b-16c0d54bd861 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-16-generic N/A linux-backports-modules-4.4.0-16-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked
[Kernel-packages] [Bug 1552410] Re: Cannot pair mako with 2014 Subaru Forester
I tried to pair today using bluetoothctl but all I got back was Failed to pair: org.bluez.Error.AuthenticationRejected and the same "failed" message on the radio display. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
If it fixes the issue for you, well I'll be even more blown away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507863] Re: Lost ability to print on LAN printer with 3.16.0-51 kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1507863 Title: Lost ability to print on LAN printer with 3.16.0-51 kernel Status in linux package in Ubuntu: Expired Bug description: After upgrading to new kernel, attempts to print resulted in no printer activity and no error messages. Printer is Canon Maxify 2320 using Canon Linux drivers and is attached via LAN. Rebooted into -50 kernel and printing worked normally again. Symptom is print job shows up in queue but is never sent to printer. Scanning function of printer works. Confirmed on following real machine installs Distro version arch kernel Lubuntu 14.04 323.13.0-66 Lubuntu 14.04 643.13.0-66 Lubuntu 14.04 323.16.0-51 Ubuntu12.04 323.13.0-66 Ubuntu14.04 643.16.0-51 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17 Uname: Linux 3.16.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 19 23:09:09 2015 InstallationDate: Installed on 2015-03-03 (230 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
1.18.3 is now in xenial, thanks for testing ** Changed in: xorg-server (Ubuntu) Status: Fix Committed => 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/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 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=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 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/1555434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570195] [NEW] Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
Public bug reported: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in linux package in Ubuntu: New Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Et
[Kernel-packages] [Bug 1570194] [NEW] [Dell Inspiron 3551] System will experience kernel panic on boot
Public bug reported: CID: 201411-16163 Dell Inspiron 3551 with OEM image (A03, 20151030) Steps: 1. Make sure reboot / cold boot works fine on this system. 2. Run dist-upgrade 3. Try to reboot this system Expected result: Everything works fine. Actual result: System will experience kernel panic on boot, if you press the power button to power down / on it again, it will enter the grub menu, sometimes it will be fine to boot from there, but I do encounter the problem that it will still hitting kernel panic when booting the OS from grub. The workaround to boot back into 3.13.0-85 is to boot into the pre-installed 3.13.0-38 kernel and reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-85-generic 3.13.0-85.129 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2147 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Apr 14 00:39:48 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=f46d1944-26ea-4d7e-a7d1-8d136f8ccf97 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=b6650f0c-419a-403f-998f-fe8eecb11d1c ro locale=en_US quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.20 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X17 dmi.board.name: 030010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrX17:bd11/28/2014:svnDellInc.:pnInspiron3551:pvrX17:rvnDellInc.:rn030010:rvrD02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: X17 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 201411-16163 amd64 apport-bug staging taipei-lab trusty ** Attachment added: "2016-04-14 12.29.40.jpg" https://bugs.launchpad.net/bugs/1570194/+attachment/4636493/+files/2016-04-14%2012.29.40.jpg ** Tags added: taip ** Tags removed: taip ** Tags added: 201411-16163 taipei-lab -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570194 Title: [Dell Inspiron 3551] System will experience kernel panic on boot Status in linux package in Ubuntu: New Bug description: CID: 201411-16163 Dell Inspiron 3551 with OEM image (A03, 20151030) Steps: 1. Make sure reboot / cold boot works fine on this system. 2. Run dist-upgrade 3. Try to reboot this system Expected result: Everything works fine. Actual result: System will experience kernel panic on boot, if you press the power button to power down / on it again, it will enter the grub menu, sometimes it will be fine to boot from there, but I do encounter the problem that it will still hitting kernel panic when booting the OS from grub. The workaround to boot back into 3.13.0-85 is to boot into the pre-installed 3.13.0-38 kernel and reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-85-generic 3.13.0-85.129 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2147 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Apr 14 00:39:48 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=f46d1944-26ea-4d7e-a7d1-8d136f8ccf97 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 201
[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault
Unfortunately, the issue is still present. Apr 14 00:34:43 cnode17 kernel: [204922.475156] divide error: [#1] SMP Apr 14 00:34:43 cnode17 kernel: [204922.475185] Modules linked in: cpuid arc4 md4 nls_utf8 cifs vhost_net vhost macvtap macvlan nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables iptable_mangle xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter xt_CT iptable_raw ip_tables x_tables dummy bridge stp llc nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache ipmi_ssif ipmi_devintf x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev input_leds sb_edac edac_core cdc_ether nf_nat_ftp usbnet mii nf_conntrack_ftp nf_nat_pptp lpc_ich nf_conntrack_pptp nf_nat_proto_gre nf_nat_sip nf_nat nf_conntrack_sip ioa tdma ipmi_si shpchp ipmi_msghandler 8250_fintek nf_conntrack_proto_gre wmi acpi_pad nf_conntrack acpi_power_meter mac_hid bonding lp parport tcp_htcp xfs btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid ixgbe igb raid6_pq vxlan i2c_algo_bit libcrc32c ahci ip6_udp_tunnel dca udp_tunnel libahci raid1 ptp pps_core megaraid_sas raid0 mdio multipath fjes linear Apr 14 00:34:43 cnode17 kernel: [204922.476423] CPU: 2 PID: 5905 Comm: ceph-osd Not tainted 4.4.0-19-generic #35 Apr 14 00:34:43 cnode17 kernel: [204922.476469] Hardware name: Dell Inc. PowerEdge R720/0W7JN5, BIOS 2.5.2 01/28/2015 Apr 14 00:34:43 cnode17 kernel: [204922.476538] task: 8822ea962940 ti: 8822eab44000 task.ti: 8822eab44000 Apr 14 00:34:43 cnode17 kernel: [204922.476606] RIP: 0010:[] [] task_numa_find_cpu+0x23c/0x710 Apr 14 00:34:43 cnode17 kernel: [204922.476682] RSP: :8822eab47bd8 EFLAGS: 00010206 Apr 14 00:34:43 cnode17 kernel: [204922.476723] RAX: RBX: 8822eab47c78 RCX: Apr 14 00:34:43 cnode17 kernel: [204922.476789] RDX: RSI: 88239f84 RDI: 8823847efa00 Apr 14 00:34:43 cnode17 kernel: [204922.476856] RBP: 8822eab47c40 R08: 0001030c9163 R09: 0262 Apr 14 00:34:43 cnode17 kernel: [204922.476923] R10: 0185 R11: 0001b936 R12: 88470dcf6e00 Apr 14 00:34:43 cnode17 kernel: [204922.477086] R13: 000d R14: 0089 R15: 0166 Apr 14 00:34:43 cnode17 kernel: [204922.477153] FS: 7f86a7caa700() GS:88239f84() knlGS: Apr 14 00:34:43 cnode17 kernel: [204922.477222] CS: 0010 DS: ES: CR0: 80050033 Apr 14 00:34:43 cnode17 kernel: [204922.477265] CR2: 21ba73f0 CR3: 002384352000 CR4: 001426e0 Apr 14 00:34:43 cnode17 kernel: [204922.477331] Stack: Apr 14 00:34:43 cnode17 kernel: [204922.477364] 8847706be600 88479f016d70 002619b8 8822ea962940 Apr 14 00:34:43 cnode17 kernel: [204922.477450] 0089 ffc5 00016d00 0089 Apr 14 00:34:43 cnode17 kernel: [204922.477535] 8822ea962940 8822eab47c78 0211 01af Apr 14 00:34:43 cnode17 kernel: [204922.477621] Call Trace: Apr 14 00:34:43 cnode17 kernel: [204922.477660] [] task_numa_migrate+0x43e/0x9b0 Apr 14 00:34:43 cnode17 kernel: [204922.477706] [] numa_migrate_preferred+0x79/0x80 Apr 14 00:34:43 cnode17 kernel: [204922.477751] [] task_numa_fault+0x7f4/0xd40 Apr 14 00:34:43 cnode17 kernel: [204922.477795] [] ? should_numa_migrate_memory+0x55/0x130 Apr 14 00:34:43 cnode17 kernel: [204922.477845] [] handle_mm_fault+0xbc0/0x1820 Apr 14 00:34:43 cnode17 kernel: [204922.477890] [] ? SYSC_recvfrom+0x144/0x160 Apr 14 00:34:43 cnode17 kernel: [204922.477936] [] __do_page_fault+0x197/0x400 Apr 14 00:34:43 cnode17 kernel: [204922.477980] [] do_page_fault+0x22/0x30 Apr 14 00:34:43 cnode17 kernel: [204922.478025] [] page_fault+0x28/0x30 Apr 14 00:34:43 cnode17 kernel: [204922.478066] Code: 55 b0 4c 89 f7 e8 f5 c9 ff ff 48 8b 55 b0 49 8b 4e 78 48 8b 82 d8 01 00 00 48 83 c1 01 31 d2 49 0f af 86 b0 00 00 00 4c 8b 73 78 <48> f7 f1 48 8b 4b 20 49 89 c0 48 29 c1 48 8b 45 d0 4c 03 43 48 Apr 14 00:34:43 cnode17 kernel: [204922.478513] RIP [] task_numa_find_cpu+0x23c/0x710 Apr 14 00:34:43 cnode17 kernel: [204922.478561] RSP Apr 14 00:34:43 cnode17 kernel: [204922.479210] ---[ end trace 7acc418f42a233b0 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568729 Title: divide error: [#1] SMP in task_numa_migrate - handle_mm_fault Status in linux package in Ubuntu: In Progress Status
[Kernel-packages] [Bug 1570195] 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/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.laun
[Kernel-packages] [Bug 1570194] 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/1570194 Title: [Dell Inspiron 3551] System will experience kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: CID: 201411-16163 Dell Inspiron 3551 with OEM image (A03, 20151030) Steps: 1. Make sure reboot / cold boot works fine on this system. 2. Run dist-upgrade 3. Try to reboot this system Expected result: Everything works fine. Actual result: System will experience kernel panic on boot, if you press the power button to power down / on it again, it will enter the grub menu, sometimes it will be fine to boot from there, but I do encounter the problem that it will still hitting kernel panic when booting the OS from grub. The workaround to boot back into 3.13.0-85 is to boot into the pre-installed 3.13.0-38 kernel and reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-85-generic 3.13.0-85.129 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2147 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Apr 14 00:39:48 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 HibernationDevice: RESUME=UUID=f46d1944-26ea-4d7e-a7d1-8d136f8ccf97 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3551 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=b6650f0c-419a-403f-998f-fe8eecb11d1c ro locale=en_US quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware 1.127.20 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X17 dmi.board.name: 030010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrX17:bd11/28/2014:svnDellInc.:pnInspiron3551:pvrX17:rvnDellInc.:rn030010:rvrD02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: X17 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
