[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-26_06-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658101] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_07-41-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658101 Title: linux: 4.9.0-15.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.9.0-15.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1658101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658101] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 18, failed: 16
tests ran: 18, failed: 16; http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_07-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658101 Title: linux: 4.9.0-15.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.9.0-15.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1658101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-26_06-55-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
As of 2017-01-26, I experience this bug on two 16.10 boxes. This kswap0d behavior is 100% reproductible when I copy large files (more than c. 500 Mo) from or to a NTFS hard drive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 2
tests ran: 4, failed: 2; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_06-05-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_05-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_04-57-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
#57 Thank you SO MUCH! That script worked perfectly for me! -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns
I can't reproduce the issue on Fedora 4.9.5-200.fc25.x86_64 either. As you pointed out, setting the fsuid/fsgid to a known userns mapping does work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659087 Title: open(2) returns EOVERFLOW within tmpfs+userns Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when creating a file in tmpfs with user namespace enabled. This issue wasn't present in 4.4.0-47 and has probably been introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964 Step to reproduce: $ unshare -r -U -m /bin/bash # mount -t tmpfs tmpfs /mnt # echo $$ 2354 In another terminal: $ sudo nsenter -t 2354 -m # touch /mnt/foo touch: cannot touch '/mnt/foo': Value too large for defined data type Note that we are not joining the user namespace when creating the file but we would expect `touch' to succeed and create the file with an inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze
Your version. I don't have any other 107 installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658270 Title: Backport Dirty COW patch to prevent wineserver freeze Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi apps freezing wineserver and leaving it unkillable: https://bugs.winehq.org/show_bug.cgi?id=41637 I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it is probably affected. A patch is available: https://lkml.org/lkml/2017/1/5/13 --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jhansonxi 2775 F pulseaudio /dev/snd/controlC2: jhansonxi 2775 F pulseaudio /dev/snd/controlC0: jhansonxi 2775 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/vg0-lv1 ro quiet nosplash ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout WifiSyslog: _MarkForUpload: True dmi.bios.date: 11/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657907] Re: 555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes
Hello Joseph, thanks for looking into this. I've downloaded the .deb files, removed all virtualbox packages, and installed the .deb files. I'll test for a few days and let you know my findings. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657907 Title: 555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes Status in linux package in Ubuntu: Incomplete Bug description: Every not too often, my wifi adapter/driver/firmware seems to crash. Here is the most recent one, entry in `dmesg`: [20634.804968] ath10k_pci :3a:00.0: firmware crashed! (uuid a373e5e5-e4a9-4391-b091-f6c7b58f9f73) [20634.804985] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [20634.804989] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [20634.805896] ath10k_pci :3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [20634.806401] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [20634.806415] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [20634.808476] ath10k_pci :3a:00.0: firmware register dump: [20634.808486] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [20634.808492] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [20634.808497] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [20634.808502] ath10k_pci :3a:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [20634.808507] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00910712 0x 0x0091080D [20634.808513] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x 0x0041E0DC [20634.808518] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 0xC09860FA [20634.808523] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 0x0018 0x004313B8 [20634.808528] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 0x00429548 [20634.808533] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x 0x0002 [20634.808538] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10 [20634.808543] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x0001 [20634.808548] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 0x004041D0 [20634.808553] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [20634.808558] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [20634.911972] ieee80211 phy0: Hardware restart was requested The system does recover, at least partially, but system feels laggy. Might be subjective. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruud 2685 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b InstallationDate: Installed on 2016-11-08 (74 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd09/13/2016:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruud 2685 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=2f2d2c45-4fef-49ec-932a-8314b15c2f6b InstallationDate: Installed on 2016-11-08 (74 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-3
[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8
Excellent, first try lucky. I downloaded all three requested kernel packages. Started with the: 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ And this version already corrects the entire issue seen with the 4.4.0-59-generic official 16.04 version. Here is the console output from applying it: mdlueck@ldslnx01:/srv/shares/data/Download/OpenSource/Ubuntu/Xenial/Bugs/1656605_ServerNoConsoleDisplay/v4.5-wily$ sudo dpkg -i linux-image-4.5.0-040500-generic_4.5.0-040500.201603140130_i386.deb Selecting previously unselected package linux-image-4.5.0-040500-generic. (Reading database ... 59100 files and directories currently installed.) Preparing to unpack linux-image-4.5.0-040500-generic_4.5.0-040500.201603140130_i386.deb ... Done. Unpacking linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ... Setting up linux-image-4.5.0-040500-generic (4.5.0-040500.201603140130) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic update-initramfs: Generating /boot/initrd.img-4.5.0-040500-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.5.0-040500-generic /boot/vmlinuz-4.5.0-040500-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.10.0-041000rc4-generic Found initrd image: /boot/initrd.img-4.10.0-041000rc4-generic Found linux image: /boot/vmlinuz-4.5.0-040500-generic Found initrd image: /boot/initrd.img-4.5.0-040500-generic Found linux image: /boot/vmlinuz-4.4.0-59-generic Found initrd image: /boot/initrd.img-4.4.0-59-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done I will stay booted to this kernel version. Please let me know if I may be of further assistance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656605 Title: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Today I did our first production 14.04 to 16.04 LTS server upgrade. I had done so a couple of times successfully on test server machines. Upon booting up on the 16.04 system/kernel, after the Grub screen the server console screen is completely blank. Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those hotkeys does toggle through the tty screens. There is no boot process logged to the server console screen. I did have the last 14.04 kernel yet installed, so selected that one from the Grub menu. Booting that 14.04 kernel, then server console display behaves normally. So I suspected perhaps a bum install of the 16.04 kernel. I used the following commands while booted to the 14.04 kernel to reinstall the 16.04 kernel: $ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic linux-image-generic $ sudo apt-get install linux-image-generic Same results booting the 16.04 kernel after those steps. Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
I have this problem with my Plantronics BackBeat. Device is connected, but I can't use it at all. a2dp.py does not help. It tells me pulseAudio service does not run. ./a2dp.py Connection MADE Selecting device: 1. 0C:E0:E4:9E:73:7C PLT_BBTSENSE 2. 98:FD:B4:0D:74:E7 ThinkPad Bluetooth Laser Mouse Select device[1]: 1 Device MAC: 0C:E0:E4:9E:73:7C Command: pacmd list-sinks failed with status: 1 stderr: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst. -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
hello, very interesting. I have similar experience with KabyLake mobil-CPU i5-7200 on Lenovo 710S Notebook. I tried also Fedora 25 live 64bit and all Ubuntu kernel higher than 4.4 failed. 17.04 (build 2017-01-25), kernel from Ubuntu mainline 4.9.5 failed to boot. Only all 16.04.1 4.4 kernel and build (until 2017-01-25) works fine. With kernel higher than 4.4 grub start and crash with purple screen: "Loading initla ramdisk _" I documented here: https://forums.lenovo.com/t5/Linux-Discussion/IdeaPad710s-80VQ0053GE-kabyLake-i5-7200-only-boots-Kernel-4-4-e/td-p/3552483 I use full-encrypted nve-ssd Intel 600p but also live-USB-Images don't work. Shall I raise a new bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: Confirmed Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2017-01-25 17:21 EDT--- Mike, If you are running the modified QEMU in a host, you are correct. You only need to patch the guest kernel if the QEMU in the host does not contain the patches I pointed here. I suggest the inclusion of both QEMU and kernel patches in order to cover any combinations. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq:
[Kernel-packages] [Bug 1659417] [NEW] docker gives "permission denied" errors with overlayfs in some scenarios
Public bug reported: Some docker users are getting a "permission denied" error with overlayfs in some situations. When a user has search permissions on the upper dir but not the lower dir they may get this error, where having search permissions for the upper dir should be sufficient. This is fixed by upstream commit 38b78a5f18584db6fa7441e0f4531b283b0e6725. Originally reported at https://github.com/docker/docker/issues/28391. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659417 Title: docker gives "permission denied" errors with overlayfs in some scenarios Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Some docker users are getting a "permission denied" error with overlayfs in some situations. When a user has search permissions on the upper dir but not the lower dir they may get this error, where having search permissions for the upper dir should be sufficient. This is fixed by upstream commit 38b78a5f18584db6fa7441e0f4531b283b0e6725. Originally reported at https://github.com/docker/docker/issues/28391. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
OK, so this is annoying race condition, so bisecting it has been causing me some pain today. It turns out that 4.10-rc4 seems OK, whereas 4.10-rc3 and before will hang after two or 3 iterations of my stress test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present Status in linux package in Ubuntu: In Progress Bug description: Ubuntu 16.04.1 Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi
Hi everyone, I had the same wifi/bluetooth interference problem. My setup is as follows: - Ubuntu 14.04 with custom-built vanilla kernel 4.3.0 - Lenovo B50 laptop having QCA9565 / AR9565 Wireless Network Adapter (ath9k) onboard - Linksys WRT-54GL router running DD-WRT v24-sp2 (10/10/09) mini - Marshall Acton bluetooth speaker Initially when I was streaming audio to the speaker, wifi degraded dramatically. After doing some research, I have successfully resolved the issue. What I have done is: * On my laptop: - added ``` Enable=Source Disable=Socket AutoConnect=True ``` to /etc/bluetooth/audio.conf - Added ``` options iwlwifi 11n_disable=1 bt_coex_active=1 ``` to /etc/modprobe.d/iwlwifi.conf However, since I'm not using iwlwifi, I'm not sure whether this had had any effect whatsoever. * On my router: - Under Wireless / Advanced Settings, I set "Bluetooth Coexistence Mode" to "Preemption" Then I've rebooted everything just in case. FYI, I encourage you to read through https://wireless.wiki.kernel.org/en/users/documentation/bluetooth- coexistence to find out what bluetooth coexistence is, and I wonder why everybody keeps switching it off (by setting bt_coex_active=0). On the contrary, this technique is designed to defeat interference problem. Also, you may find nice to add "load-module module-switch-on-connect" to /etc/pulse/default.pa so that audio starts streaming to bluetooth speaker automatically when it connects (and then back to laptop speakers when it disconnects.) Cheers, PD. -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658999 Title: [Xenial Regression] Kernel panics on HDMI in Xenial Status in linux package in Ubuntu: Triaged Bug description: sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a wide range of displays. He's running 4.4.0-62.83 and notes this is definitely a regression as it was working previously. Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995791] [ cut here ] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995842] WARNING: CPU: 4 PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995846] WARN_ON(!wm_changed) Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995849] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152 v4l2_common hid_multitouch mii videodev snd media joydev input_leds serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800 intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf industrialio kvm_intel kvm irqbypass iptable_filter ip_tables ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4 usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi pinctrl_sunrisepoint video pinctrl_intel fjes Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996021] CPU: 4 PID: 2548 Comm: Xorg Tainted: P O4.4.0-62-generic #83-Ubuntu Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996024] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996027] 0286 5b61ce69 880880293920 813f7c63 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996033] 880880293968 c02be9a0 880880293958 810812d2 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996037] 88089255f000 88089160a148 88089255e000 880892644b78 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996042] Call Trace: Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996051] [] dump_stack+0x63/0x90 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996059] [] warn_slowpath_common+0x82/0xc0 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996064] [] warn_slowpath_fmt+0x5c/0x80 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996101] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996136] [] skl_update_wm+0x185/0x610 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996190] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996225] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996276] [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996327] [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996366] [] ? drm_atomic_check_only+0x18e/0x590 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996397] [] drm_atomic_commit+0x37/0x60 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996415] [] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996443] [] drm_mode_set_config_internal+0x62/0x100 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996472] [] drm_mode_setcrtc+0x3cc/0x4f0 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996493] [] drm_ioctl+0x152/0x540 [drm] Jan 24 08:32:3
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Changed in: qemu (Ubuntu) Assignee: Jon Grimm (jgrimm) => (unassigned) ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Ubuntu Server Team (ubuntu-server) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
In my testing, only qemu-system-ppc version 1:2.6.1+dfsg-0ubuntu5.2 available in yakkety and the template to set -cpu POWER8NVL was needed to resolve the issue. No kernel patches were necessary. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel int
[Kernel-packages] [Bug 1659075] Re: Live media lacks functioning driver for AMD Polaris GPUs, resulting in X failing to start and unusable text console
We're talking about the live/install media... throwing the image on a USB drive and booting it, for trialling or installing the OS. I have not tried the 16.04 (not .1) media. However, I wouldn't expect different results. ...How would I install an alternate kernel on the live image? In the installed system, using the linux-image-generic-hwe-16.04-edge kernel shows improvement (removes the need for nomodeset and allows X to enumerate and configure the card's outputs) but doesn't completely fix the issue. To get hardware acceleration, it's necessary to install libgl1-mesa-dri >=11.3 which isn't available from the official repositories. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659075 Title: Live media lacks functioning driver for AMD Polaris GPUs, resulting in X failing to start and unusable text console Status in linux package in Ubuntu: Incomplete Bug description: The text console flickers, and ignores most keyboard input. This can be worked around by adding nomodeset to the kernel command line, which will make X fall back on the VESA driver, with all the limitations inherent to that. The resulting installed system will have the same problem, which can alternately be worked around by installing linux-image-generic- hwe-16.04-edge, but this only partially fixes the problem. The Mesa radeonsi driver in Xenial is too old for these GPUs, so while modesetting and display configuration will now be functional, the system will still entirely lack graphics acceleration. The only workarounds I know of for this is to source a newer Mesa from a PPA or similar, or install AMD's proprietary drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.31.33 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-gnome 4365 F pulseaudio /dev/snd/controlC1: ubuntu-gnome 4365 F pulseaudio CasperVersion: 1.376 Date: Tue Jan 24 18:25:03 2017 IwConfig: lono wireless extensions. enp3s0no wireless extensions. LiveMediaBuild: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash nomodeset BOOT_IMAGE=/casper/vmlinuz.efi 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-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
Added tracker for qemu package given speculation that may need updated for POWER8NVL processor in comment #14. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: h
[Kernel-packages] [Bug 1656112] WifiSyslog.txt
Default Comment by Bridge ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809064/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To mana
[Kernel-packages] [Bug 1656112] nvram.gz
Default Comment by Bridge ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1656112/+attachment/4809065/+files/nvram.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notificati
[Kernel-packages] [Bug 1656112] UdevDb.txt
Default Comment by Bridge ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809063/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifi
[Kernel-packages] [Bug 1656112] ProcPpc64.tar.gz
Default Comment by Bridge ** Attachment added: "ProcPpc64.tar.gz" https://bugs.launchpad.net/bugs/1656112/+attachment/4809062/+files/ProcPpc64.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To
[Kernel-packages] [Bug 1656112] ProcModules.txt
Default Comment by Bridge ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809061/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To ma
[Kernel-packages] [Bug 1656112] ProcMisc.txt
Default Comment by Bridge ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809060/+files/ProcMisc.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage n
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Jon Grimm (jgrimm) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface t
[Kernel-packages] [Bug 1656112] Dependencies.txt
Default Comment by Bridge ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809053/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To
[Kernel-packages] [Bug 1656112] ProcCpuinfo.txt
Default Comment by Bridge ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809058/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To ma
[Kernel-packages] [Bug 1656112] OpalElog.tar.gz
Default Comment by Bridge ** Attachment added: "OpalElog.tar.gz" https://bugs.launchpad.net/bugs/1656112/+attachment/4809057/+files/OpalElog.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To ma
[Kernel-packages] [Bug 1656112] DeviceTree.tar.gz
Default Comment by Bridge ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/1656112/+attachment/4809054/+files/DeviceTree.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 T
[Kernel-packages] [Bug 1656112] JournalErrors.txt
Default Comment by Bridge ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809055/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 T
[Kernel-packages] [Bug 1656112] Lspci.txt
Default Comment by Bridge ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809056/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifica
[Kernel-packages] [Bug 1656112] ProcInterrupts.txt
Default Comment by Bridge ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1656112/+attachment/4809059/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8
[Kernel-packages] [Bug 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial
I built the attached patch and put the binaries at [1]. It would be nice to have someone test it before we push it for review and maybe respin. [1] http://people.canonical.com/~cascardo/lp1658999/ ** Patch added: "0001-UBUNTU-SAUCE-i915_bpo-change-WARN_ON-wm_changed-to-n.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658999/+attachment/4809051/+files/0001-UBUNTU-SAUCE-i915_bpo-change-WARN_ON-wm_changed-to-n.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658999 Title: [Xenial Regression] Kernel panics on HDMI in Xenial Status in linux package in Ubuntu: Triaged Bug description: sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a wide range of displays. He's running 4.4.0-62.83 and notes this is definitely a regression as it was working previously. Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995791] [ cut here ] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995842] WARNING: CPU: 4 PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995846] WARN_ON(!wm_changed) Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995849] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152 v4l2_common hid_multitouch mii videodev snd media joydev input_leds serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800 intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf industrialio kvm_intel kvm irqbypass iptable_filter ip_tables ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4 usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi pinctrl_sunrisepoint video pinctrl_intel fjes Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996021] CPU: 4 PID: 2548 Comm: Xorg Tainted: P O4.4.0-62-generic #83-Ubuntu Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996024] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996027] 0286 5b61ce69 880880293920 813f7c63 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996033] 880880293968 c02be9a0 880880293958 810812d2 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996037] 88089255f000 88089160a148 88089255e000 880892644b78 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996042] Call Trace: Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996051] [] dump_stack+0x63/0x90 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996059] [] warn_slowpath_common+0x82/0xc0 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996064] [] warn_slowpath_fmt+0x5c/0x80 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996101] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996136] [] skl_update_wm+0x185/0x610 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996190] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996225] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996276] [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996327] [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996366] [] ? drm_atomic_check_only+0x18e/0x590 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996397] [] drm_atomic_commit+0x37/0x60 [drm] Jan 24 08:32:
[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** Also affects: qemu (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/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in qemu source package in Xenial: New Bug description: Upon running the virtualization test from the certification test suite, the kvm guest test fails with the following error: kvm_init_vcpu failed: Invalid argument This same test works on multiple other IBM Power 8 and Openpower servers. kvm-ok tells us that kvm virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu-system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Kernel-packages] [Bug 1659075] Re: Live media lacks functioning driver for AMD Polaris GPUs, resulting in X failing to start and unusable text console
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659075 Title: Live media lacks functioning driver for AMD Polaris GPUs, resulting in X failing to start and unusable text console Status in linux package in Ubuntu: Incomplete Bug description: The text console flickers, and ignores most keyboard input. This can be worked around by adding nomodeset to the kernel command line, which will make X fall back on the VESA driver, with all the limitations inherent to that. The resulting installed system will have the same problem, which can alternately be worked around by installing linux-image-generic- hwe-16.04-edge, but this only partially fixes the problem. The Mesa radeonsi driver in Xenial is too old for these GPUs, so while modesetting and display configuration will now be functional, the system will still entirely lack graphics acceleration. The only workarounds I know of for this is to source a newer Mesa from a PPA or similar, or install AMD's proprietary drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.31.33 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-gnome 4365 F pulseaudio /dev/snd/controlC1: ubuntu-gnome 4365 F pulseaudio CasperVersion: 1.376 Date: Tue Jan 24 18:25:03 2017 IwConfig: lono wireless extensions. enp3s0no wireless extensions. LiveMediaBuild: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash nomodeset BOOT_IMAGE=/casper/vmlinuz.efi 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-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659087 Title: open(2) returns EOVERFLOW within tmpfs+userns Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when creating a file in tmpfs with user namespace enabled. This issue wasn't present in 4.4.0-47 and has probably been introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964 Step to reproduce: $ unshare -r -U -m /bin/bash # mount -t tmpfs tmpfs /mnt # echo $$ 2354 In another terminal: $ sudo nsenter -t 2354 -m # touch /mnt/foo touch: cannot touch '/mnt/foo': Value too large for defined data type Note that we are not joining the user namespace when creating the file but we would expect `touch' to succeed and create the file with an inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659268] Re: Consistent boot time kernel panic
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5 ** Tags added: kernel-da-key yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659268 Title: Consistent boot time kernel panic Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.162 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago) dmi.bios.date: 04/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE6WW (2.26 ) dmi.board.name: 2007GCG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007GCG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659268] Re: Consistent boot time kernel panic
Do you know what kernel version this panic starts happening in? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659268 Title: Consistent boot time kernel panic Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.162 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago) dmi.bios.date: 04/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE6WW (2.26 ) dmi.board.name: 2007GCG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007GCG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug: 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ 4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ 4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/ 4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/ You don't have to test every kernel, just up until the kernel that first has this bug. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Zesty) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => High ** Tags added: performing-bisect zesty ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Status in linux source package in Zesty: Confirmed Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.
[Kernel-packages] [Bug 1659381] Re: linux: 4.8.0-37.39 -proposed tracker
Backport packages from packages here can be worked on, the following tracking bugs were opened for them: linux-hwe-edge (16.04.1) - bug 1659382 ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + kernel-stable-phase-changed:Wednesday, 25. January 2017 18:17 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Wednesday, 25. January 2017 18:17 UTC kernel-stable-phase:Packaging + + -- swm properties -- + derivative-trackers-created: true + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659381 Title: linux: 4.8.0-37.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Wednesday, 25. January 2017 18:17 UTC kernel-stable-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1659381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
When I collected information with "apport-collect 1659340" I had booted with the 4.4.0-45 kernel, which works for me. Therefore I suppose that some of the collected information is irrelevant. I can't boot with any later kernel that I've tried. ** 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/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Confirmed Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659381] [NEW] linux: 4.8.0-37.39 -proposed tracker
Public bug reported: This bug is for tracking the 4.8.0-37.39 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Wednesday, 25. January 2017 18:17 UTC kernel-stable-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: block-proposed block-proposed-yakkety kernel-release-tracking-bug yakkety ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-yakkety ** Tags added: yakkety ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-pa
[Kernel-packages] [Bug 1659340] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809042/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809043/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809046/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809045/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809047/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809048/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809050/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809049/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809044/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809039/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809037/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809038/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Re: Linux kernel 4.8 hangs at boot up
apport information ** Tags added: apport-collected yakkety ** Description changed: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. + --- + ApportVersion: 2.20.3-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: kjell 2022 F pulseaudio + /dev/snd/controlC1: kjell 2022 F pulseaudio + /dev/snd/controlC0: kjell 2022 F pulseaudio + CurrentDesktop: GNOME-Flashback:Unity + DistroRelease: Ubuntu 16.10 + HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb + InstallationDate: Installed on 2013-09-25 (1218 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) + MachineType: Acer Aspire V5-551G + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-45-generic N/A + linux-backports-modules-4.4.0-45-generic N/A + linux-firmware1.161.1 + Tags: yakkety + Uname: Linux 4.4.0-45-generic x86_64 + UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/11/2013 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V2.14 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Havok + dmi.board.vendor: Acer + dmi.board.version: Type2 - A01 Board Version + dmi.chassis.type: 10 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: + dmi.product.name: Aspire V5-551G + dmi.product.version: V2.14 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809036/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872]
[Kernel-packages] [Bug 1659340] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809040/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1659340/+attachment/4809041/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kjell 2022 F pulseaudio /dev/snd/controlC1: kjell 2022 F pulseaudio /dev/snd/controlC0: kjell 2022 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=d42f8b71-8244-45d9-a814-ca7b9fb474bb InstallationDate: Installed on 2013-09-25 (1218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V5-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=b953dea5-2c7a-4d65-9b8e-446b111ccce8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.4.0-45-generic x86_64 UpgradeStatus: Upgraded to yakkety on 2016-10-26 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/11/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.14:bd03/11/2013:svnAcer:pnAspireV5-551G:pvrV2.14:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V5-551G dmi.product.version: V2.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Hi I'd like to implement Cascardo kernel since I've been having the same issue, though not on all of the xenial machines running 4.4.0-59-generic which is strange. Could someone tell how to implement Cascardo kernel without completely messing up my machine. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Triaged Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)
Can you test the following two early Yakkety kernels: 4.6.0-10: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/10600030 4.8.0-11: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/10923199 With these kernels, you need to install both the linux-image and linux- image-extra .deb packages. ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657994 Title: Regression: HDMI audio produces no sound (Skylake NUC) Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no longer produces sound. * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine * Audio from headphone jack works fine * Userspace seems to be happily playing to HDMI audio device, but no sound produced at HDMI sink (Samsung TV) Any of a wide range of pre-built mainline kernels fail to produce HDMI audio, but with a different failure mode (HDMI audio does not seem to be enumerated in the same way as in the Ubuntu kernels.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: israel 1973 F pulseaudio /dev/snd/controlC1: israel 1973 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 20 08:58:35 2017 HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c InstallationDate: Installed on 2016-10-03 (108 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-405 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657994/+subscriptions -- Mailing list: https://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 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel
It will be a couple of weeks before I can physically get to the system again. So if you have other kernel versions you would like me to test, please list them all and I can test them all at once. Sent from my mobile device On Jan 25, 2017 10:21, "Joseph Salisbury" wrote: > So the 3.13 final kernel hits the panic, but the 4.4 final kernel does > not, using the links posted in comment #19? > > > Can you also test the Xenial -proposed kernel? It is available from: > https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/ > 11877924 > > For that kernel, you need to install both the linux-image and linux- > image-extra .deb packages. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1653162 > > Title: > System won't boot after upgrade to 16.04 with 4.4.0 kernel > > Status in linux package in Ubuntu: > Triaged > Status in linux source package in Xenial: > Triaged > Status in linux source package in Yakkety: > Triaged > > Bug description: > I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in > it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to > 16.04.1 the system won't boot. It can't find the root filesystem. I > see errors about host adapter dead on the screen many times. This is > with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel > 3.13.0-105 the system boots just fine. > > I have mptbios 5.06.04. > The CERC card says bios version 4.1-0 [Build 7403] > > When booting into the ercovery kernel I'm getting error messages about > host adapter dead. > Eventually I get a message: > "aacraid: aac_fib_send: first asynchronous command timed out. > Usually a result of a PCI interrupt routing problem > update moher board BIOS or consider utilizing one of > the SAFE mode kernel options (acpi, apic etc)" > > > Using kernel parameter "intel_iommu=on" doesn't help. This was suggested > on a post that I saw about these errors. > > Booting with "noapic" didn't help. > Booting with "noapic noacpi" didn't help. > > > I've also tried the dkms modules from Adaptec and that doesn't seem to > help either. > > > I can't figure out how to upgrade the firmware or BIOS on the system > from Ubuntu either. > > > This may be related to this bug: https://bugs.launchpad.net/ > ubuntu/+source/linux/+bug/1552551?comments=all > --- > ApportVersion: 2.20.1-0ubuntu2.4 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > DistroRelease: Ubuntu 16.04 > HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 > InstallationDate: Installed on 2014-02-24 (1039 days ago) > InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 > (20130820.1) > IwConfig: >eth1 no wireless extensions. > >lono wireless extensions. > 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: Dell Computer Corporation PowerEdge 1800 > Package: linux (not installed) > ProcEnviron: >TERM=screen >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 radeondrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic > root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth > ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-3.13.0-105-generic N/A >linux-backports-modules-3.13.0-105-generic N/A >linux-firmware 1.157.6 > RfKill: > > Tags: xenial > Uname: Linux 3.13.0-105-generic x86_64 > UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 09/01/2004 > dmi.bios.vendor: Dell Computer Corporation > dmi.bios.version: A00 > dmi.board.name: 0X7500 > dmi.board.vendor: Dell Computer Corporation > dmi.board.version: A00 > dmi.chassis.type: 17 > dmi.chassis.vendor: Dell Computer Corporation > dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004: > svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation: > rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: > dmi.product.name: PowerEdge 1800 > dmi.sys.vendor: Dell Computer Corporation > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1653162/+subscriptions > > -- You received this bug notification b
[Kernel-packages] [Bug 1659340] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1659340 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/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: Incomplete Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656605] Re: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8
Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc4. We first need to identify the last bad kernel and first good one. Can you test the following kernels: 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ 4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/ 4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/ You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug. We can SRU the commit to all releases this bug affects once we identify it. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1656605 Title: No server console display after Grub screen until fully booted and pressing Ctrl-Alt-F1/8 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Today I did our first production 14.04 to 16.04 LTS server upgrade. I had done so a couple of times successfully on test server machines. Upon booting up on the 16.04 system/kernel, after the Grub screen the server console screen is completely blank. Someone suggested using Ctrl-Alt-F1/8, and indeed pressing those hotkeys does toggle through the tty screens. There is no boot process logged to the server console screen. I did have the last 14.04 kernel yet installed, so selected that one from the Grub menu. Booting that 14.04 kernel, then server console display behaves normally. So I suspected perhaps a bum install of the 16.04 kernel. I used the following commands while booted to the 14.04 kernel to reinstall the 16.04 kernel: $ sudo dpkg -P linux-image-4.4.0-59-generic linux-image-extra-4.4.0-59-generic linux-image-generic $ sudo apt-get install linux-image-generic Same results booting the 16.04 kernel after those steps. Hardware spec is an Intel Atom D945GCLF2D boxed motherboard with Intel Atom 330 Dual-Core processor and 2GB RAM. RAID is 3Ware SATA RAID. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656875] Re: fanatic enable/disable docker broken with docker.io >= 1.12
This bug was fixed in the package ubuntu-fan - 0.12.1 --- ubuntu-fan (0.12.1) zesty; urgency=low * fanatic: Support new (>=1.12) docker network management commands (LP: #1656875). * dep8: Added ADT test case for docker. This also required a minor change to the test setup in fanatic to suppress output to stderr. -- Stefan Bader Tue, 17 Jan 2017 14:26:49 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1656875 Title: fanatic enable/disable docker broken with docker.io >= 1.12 Status in ubuntu-fan package in Ubuntu: Fix Released Bug description: The way docker handles networks changed when moving to newer docker versions. Networks are now created/deleted by "docker network" commands (similar to LXD). This needs to be handled by fanatic when doing docker related tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1656875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658101] Re: linux: 4.9.0-15.16 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658101 Title: linux: 4.9.0-15.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 4.9.0-15.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1658101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel
So the 3.13 final kernel hits the panic, but the 4.4 final kernel does not, using the links posted in comment #19? Can you also test the Xenial -proposed kernel? It is available from: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/11877924 For that kernel, you need to install both the linux-image and linux- image-extra .deb packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653162 Title: System won't boot after upgrade to 16.04 with 4.4.0 kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to 16.04.1 the system won't boot. It can't find the root filesystem. I see errors about host adapter dead on the screen many times. This is with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel 3.13.0-105 the system boots just fine. I have mptbios 5.06.04. The CERC card says bios version 4.1-0 [Build 7403] When booting into the ercovery kernel I'm getting error messages about host adapter dead. Eventually I get a message: "aacraid: aac_fib_send: first asynchronous command timed out. Usually a result of a PCI interrupt routing problem update moher board BIOS or consider utilizing one of the SAFE mode kernel options (acpi, apic etc)" Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a post that I saw about these errors. Booting with "noapic" didn't help. Booting with "noapic noacpi" didn't help. I've also tried the dkms modules from Adaptec and that doesn't seem to help either. I can't figure out how to upgrade the firmware or BIOS on the system from Ubuntu either. This may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 InstallationDate: Installed on 2014-02-24 (1039 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth1 no wireless extensions. lono wireless extensions. 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: Dell Computer Corporation PowerEdge 1800 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.157.6 RfKill: Tags: xenial Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A00 dmi.board.name: 0X7500 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A00 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491654] Re: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation
Thanks for the update. We can perform a "Reverse" bisect to identify the commit that fixes the bug in v4.10-rc3. We first need to identify the last bad kernel and first good one. Can you test the following kernels: 3.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/ 3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/ 4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ 4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/ 4.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/ You don't have to test every kernel, just up until the kernel that first kernel that does not have this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491654 Title: Intel P3700 PCIe SSD string shows ''Unknown'' during Ubuntu 14.04 installation Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: Current Behavior == 1. Intel P3700 PCIe SSD string shows "Unknow" during Ubuntu 14.04 install. Reference Verification == 1. Which version of previous BIOS/BMC/HW passed/failed? 1st Test 2. Which similar project/product passed/failed? NA Steps to reproduce the problem == 1. Install Intel P3700 PCIe SSD*2 and SAS 12G HDD*8 with LSI 3108 into SUT. 2. Power on system and install Ubuntu 14.04. 3. Intel P3700 PCIe SSD string shows "Unknown" during OS install. Expected Behavior == 1. Intel P3700 PCIe SSD string should not show "Unknown" during Ubuntu 14.04 install. Pcie SSD config:HDD/SSD:Intel,SSDPE2MD016T4,PCI-e,1.6TB,Gen3 Copied from private bug: https://bugs.launchpad.net/quantatw/+bug/1454965 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658270] Re: Backport Dirty COW patch to prevent wineserver freeze
The stock 3.13.0-107 from the repository works find, or my -107 kernel posted in comment #15? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658270 Title: Backport Dirty COW patch to prevent wineserver freeze Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: A few kernels updates ago (after kernel 3.13.0-98) on 14.04 (Trusty) a backported fix for Dirty COW from kernel 4.8.3 resulted in some Delphi apps freezing wineserver and leaving it unkillable: https://bugs.winehq.org/show_bug.cgi?id=41637 I haven't tested for the bug on 16.04 Xenial (kernel 4.4.0-59) but it is probably affected. A patch is available: https://lkml.org/lkml/2017/1/5/13 --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jhansonxi 2775 F pulseaudio /dev/snd/controlC2: jhansonxi 2775 F pulseaudio /dev/snd/controlC0: jhansonxi 2775 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6c1d3a04-0529-476c-b193-3e584c0333ca JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/vg0-lv1 ro quiet nosplash ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout WifiSyslog: _MarkForUpload: True dmi.bios.date: 11/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1206:bd11/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659340] [NEW] Linux kernel 4.8 hangs at boot up
Public bug reported: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. ** 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/1659340 Title: Linux kernel 4.8 hangs at boot up Status in linux package in Ubuntu: New Bug description: I've got an Acer Aspire V5-551G with a 64-bit AMD processor with dual boot, Windows 10 and Ubuntu 16.10. Ubuntu can be started and runs without problems with Linux kernel 4.4.0-45. When I try to start with any of the 4.8.0 kernels delivered with regular Ubuntu updates, they all hang after printing Läser in Linux 4.8.0-34-generic ... Läser in initial ramdisk ... Sorry for the partly Swedish text. I guess that the lines would start with "Loading" instead of "Läser in" on an English version. The behaviour is the same with all 4.8.0 versions up to the latest 4.8.0-34 and with -generic, -generic (upstart) and -generic (recovery mode). After a while the fan runs at full speed, as if the processor is working hard, but nothing happens. After I've tried in vain to start with Linux 4.8.0-xx, and then starts with 4.4.0-45, the following errors are usually printed: [ 2.511733] usb 4-3: string descriptor 0 read error: -22 [ 3.841872] [drm:radeon_scpi_init [radeon]] *ERROR* Cannot find backlight controller /dev/sda7: clean, 807007/9363456 files, 7364300/37423360 blocks [ 21.335117] usb 4-3: string descriptor 0 read error: -22 When a successful start has not been immediately preceded by a failed start, only the line beginning "/dev/sda7" is printed. I have previously commented on bug #1635447. As recommended there, I've also tested with the upstream kernel 4.10-rc3. It worked just as bad as 4.8.0. I tried to report this bug with 'ubuntu-bug linux' after I had booted with the 4.4.0-45 kernel, but I couldn't. It said that linux-image-4.4.0-45- generic is not an official Ubuntu package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659333] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1659333 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/1659333 Title: linux 4.4.0-62.83 ADT test failure with linux 4.4.0-62.83 Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20170125_144606_ee613@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659333] [NEW] linux 4.4.0-62.83 ADT test failure with linux 4.4.0-62.83
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20170125_144606_ee613@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659333 Title: linux 4.4.0-62.83 ADT test failure with linux 4.4.0-62.83 Status in linux package in Ubuntu: Incomplete Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20170125_144606_ee613@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Thanks Tim for the clarification. I will not make any more status
changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1655683
Title:
kernel BUG at skbuff.h:1486 Insufficient linear data in skb
__skb_pull.part.7+0x4/0x6 [openvswitch]
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
In Progress
Bug description:
Since 2016-12-30 EST we have been experiencing repeated crashes of our
OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
line 1486:
1471 /**
1472 * skb_peek - peek at the head of an &sk_buff_head
1473 * @list_: list to peek at
1474 *
1475 * Peek an &sk_buff. Unlike most other operations you _MUST_
1476 * be careful with this one. A peek leaves the buffer on the
1477 * list and someone else may run off with it. You must hold
1478 * the appropriate locks or have a private queue to do this.
1479 *
1480 * Returns %NULL for an empty list or a pointer to the head element.
1481 * The reference count is not incremented and the reference is therefore
1482 * volatile. Use with caution.
1483 */
1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
1485 {
1486 struct sk_buff *skb = list_->next;
1487
1488 if (skb == (struct sk_buff *)list_)
1489 skb = NULL;
1490 return skb;
1491 }
This generally results in a full panic crash of the Neutron node and
connectivity breaking for VMs within the cloud. However, after using
crash-dumptools to collect information on the crashes over the past
three days, the kernel loaded by kexec during the crashdump appears in
about 2 out of 3 crash instances to continue running, and we see a
flap of the neutron services instead of a full panic that brings the
Neutron server down and necessitates a hard reboot.
I believe that this is a manifestation of the openvswitch and issue
described on 2017-01-08 as:
"OVS can only process L2 packets. But OVS GRE receive handler
can accept IP-GRE packets. When such packet is processed by
OVS datapath it can trigger following assert failure due
to insufficient linear data in skb."
https://patchwork.ozlabs.org/patch/712373/
I have not tested the patch provided above yet.
Other information and a few sample dmesg outputs from the crash:
(multiple dumps available)
# lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
# apt-cache policy openvswitch
N: Unable to locate package openvswitch
root@neutron01:/var/crash# apt-cache policy openvswitch-common
openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy openvswitch-switch
openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy neutron-plugin-openvswitch-agent
neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
*** 1:2014.1.5-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:2014.1.3-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1:2014.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
example dmesg:
## dmesg.201701060019
> [33100.131019] [ cut here ]
> [33100.131176] kernel BUG at
/build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
> [33100.131424] invalid opcode: [#1] SMP
> [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter
ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth
openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether
x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si
bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca
i2c_algo_bit ptp pps_core megaraid_sas mdio
> [33100.133560] CPU: 2 PID: 0 Comm: swapper/2 Not tainte
[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Apparently 4.8.0-34-generic detects my Latitude E7470 touchpad/stick as ALPS instead of BYD (4.8.0-32-generic detects as BYD). I don't know which would be the correct one, but by default ALPS is way too sensitive and I have to apply those xprops changes before it is usable again (basically I can't click anything because no matter how much I want to hold my finger still, it just goes around in circles and the pointer is not on top of an icon long enough to click it). There is also something weird about how the touchpad behaves (or maybe I noticed it now cause I use it more instead of the trackpoint?), is it supposed to scroll vertically when I move a single finger vertically on the right half of it? Basically I have to always move my finger horizontally first, otherwise it accidentally scrolls. I think it would be useful to make the BYD/ALPS configurable. The BYD driver works a lot better by default, and I think I actually prefer it over the ALPS one :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://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 1659087] Re: open(2) returns EOVERFLOW within tmpfs+userns
On Tue, Jan 24, 2017 at 09:37:18PM -, Jonathan Calmels wrote: > Interesting, I tried to reproduce with a Debian strech 4.8.0-2-amd64 > (Debian 4.8.15-2) and 4.9.0-1-amd64 (Debian 4.9.2-2) and didn't hit the > error. Odd. The commit responsible for this should be 036d523641c6 "vfs: Don't create inodes with a uid or gid unknown to the vfs" which did go into 4.8. I'll have to take another look. > This seems to be specific to tmpfs though, touching the file anywhere > else yields the nobody:nogroup mapping. It would happen for any filesystem which was mounted from within the user namespace. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659087 Title: open(2) returns EOVERFLOW within tmpfs+userns Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 4.4.0-59.80-generic 4.4.35, open(2) returns EOVERFLOW when creating a file in tmpfs with user namespace enabled. This issue wasn't present in 4.4.0-47 and has probably been introduced by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964 Step to reproduce: $ unshare -r -U -m /bin/bash # mount -t tmpfs tmpfs /mnt # echo $$ 2354 In another terminal: $ sudo nsenter -t 2354 -m # touch /mnt/foo touch: cannot touch '/mnt/foo': Value too large for defined data type Note that we are not joining the user namespace when creating the file but we would expect `touch' to succeed and create the file with an inode set to INVALID_UID/GID (i.e. nobody:nogroup) within the mount namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659268] Re: Consistent boot time kernel panic
** Attachment added: "screen shot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+attachment/4808924/+files/IMG_20170125_123244.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659268 Title: Consistent boot time kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.162 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago) dmi.bios.date: 04/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE6WW (2.26 ) dmi.board.name: 2007GCG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007GCG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659268] 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/1659268 Title: Consistent boot time kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.162 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago) dmi.bios.date: 04/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE6WW (2.26 ) dmi.board.name: 2007GCG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007GCG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659225] Re: juju: enable ceph-rbd configuration for nova-compute-proxy charm
** Package changed: linux (Ubuntu) => charms ** Tags added: openstack-ibm ** Changed in: charms Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Also affects: ubuntu-z-systems 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/1659225 Title: juju: enable ceph-rbd configuration for nova-compute-proxy charm Status in Ubuntu on IBM z Systems: New Status in Juju Charms Collection: New Bug description: This is a request to support ceph-rbd as a backing store for cinder-deployed volumes and nova ephemeral disks as part of the compute proxy charm for KVM for z. When an openstack juju bundle gets deployed with a ceph cluster as a backing store for cinder(-ceph), the ceph-rbd client on KVM for z should be configured to communicate with this cinder-ceph, along with the necessary configurations in libvirt and nova to allow attachments of the ceph-rbd volumes/disks to the nova instances running on KVM for z. ---uname output--- Linux zfwcec082 4.4.0-40.60.el7_2.kvmibm1_1_3.2.s390x #1 SMP Tue Oct 18 14:41:51 EDT 2016 s390x s390x s390x GNU/Linux Machine Type = 2847-743 ---Steps to Reproduce--- 1. Deploy KVM on z via juju nova-compute-proxy charm (https://jujucharms.com/u/openstack-charmers-next/nova-compute-proxy/) along with ceph and cinder-ceph on other (Ubuntu) systems. 2. create a volume on ceph backend and attach to a nova instance running on KVM for z. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1659225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659268] [NEW] Consistent boot time kernel panic
Public bug reported: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=/dev/mapper/username--laptop--vg-root ro splash quiet crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.162 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-24 (0 days ago) dmi.bios.date: 04/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE6WW (2.26 ) dmi.board.name: 2007GCG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn2007GCG:pvrThinkPadT60:rvnLENOVO:rn2007GCG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007GCG dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659268 Title: Consistent boot time kernel panic Status in linux package in Ubuntu: New Bug description: I don't know to provide the necessary crash dump and any other things that may be required to analyze this. The crash occured consistently on every boot with this kernel. I'm currently running 4.8.0-32-generic, which I still have installed. It does not cause this crash. I got this since first reboot after dist-upgrade to 17.04. BTW, it is not clear how to properly report a boot time kernel panic, so I asked this question: http://askubuntu.com/questions/40792/whats-the-best-way-to-report-a-kernel-panic-bug# ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-12-generic 4.9.0-12.13 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-32-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CurrentDesktop: XFCE Date: Wed Jan 25 13:35:17 2017 HibernationDevice: RESUME=/dev/mapper/mightyiam--laptop--vg-swap_1 MachineType: LENOVO 2007GCG PccardctlIdent: Socket 0: no product info available P
[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-25_11-17-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp4__4.8.0-36.38__2017-01-25_11-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-25_11-21-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-25_11-25-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-25_11-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp4__4.8.0-36.38__2017-01-25_11-26-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting
I try install Ubuntu14.04 in RAID1 and update mainline kernel v4.10-rc3. It reboots successfully without any error. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1648388 Title: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting Status in linux package in Ubuntu: Incomplete Bug description: Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or UEFI mode. System hangs while rebooting Not found the issue in RAID0 No issue on Ubuntu14.04 Driver-OS inbox support Below as error messages === INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task jbd2/md126p2-8:1732 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task ext4lazyinit:1873 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task kworker/u66:4:3139 blocked for more than 120 seconds. Not tainted 4.4.0-21-generic #37-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. === WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't hang while rebooting: vm.dirty_background_ratio=5 vm.dirty_ratio=10 kernel.panic=3 kernel.hung_task_panic=1 kernel.hung_task_timeout_secs=30 --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b InstallationDate: Installed on 2016-12-15 (10 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Dell DCS6430G Package: linux (not installed) ProcEnviron: LANGUAGE=en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: xenial Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/22/2016 dmi.bios.vendor: Dell dmi.bios.version: 2.0.3 dmi.board.name: 038VV0 dmi.board.vendor: Dell dmi.board.version: X01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell dmi.modalias: dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr: dmi.product.name: DCS6430G dmi.sys.vendor: Dell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-25_11-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652264] Re: [HP Spectre 13-v006ur] Laptop wakes up by itself in a second after suspend
Problem starts in v4.8 (c8d2bc9bc39ebea8437fd974fdbc21847bb897a3) Additionally in 4.8 I got warnings about missing firmware: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 With previous package v4.7.10 (b3afc4525a507f21e98cc7571ea8c3f28484241c) suspend works well and no warnings about missing firmware. I think many thanks to Intel about it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652264 Title: [HP Spectre 13-v006ur] Laptop wakes up by itself in a second after suspend Status in linux package in Ubuntu: Incomplete Bug description: All waking devices are disabled: root@spectre:~# acpitool -w | grep enabled 51. PWRBS4*enabled platform:PNP0C0C:00 root@spectre:~# BIOS is latest. Suspend works well with 4.4 With 4.9 symptoms thee same... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-32-generic 4.8.0-32.34 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1515 F pulseaudio Date: Fri Dec 23 12:35:37 2016 InstallationDate: Installed on 2016-09-29 (84 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Spectre Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic.efi.signed root=UUID=b6e97f7f-4568-4e6f-8e85-0baca5aac5b4 ro ipv6.disable=1 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.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-11-14 (38 days ago) dmi.bios.date: 08/11/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A0 dmi.board.vendor: HP dmi.board.version: 48.39 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.26:bd08/11/2016:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.39:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Spectre Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-25_11-08-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on-lan setting
I just tested it, just by installing the 4.8.0 Kernel in Ubuntu 16.04, without any workaround and Nvidia drivers enabled. Nothing changed so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450396 Title: Gigabyte P35-DS3: does not stay suspended with default "ug" wake-on- lan setting Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Bug description: === Update: This bug was reported from BIOS version F13 of my board, in the meantime I upgraded to the most recent version F14, but this had no impact on the bug. === Hello, using Suspend-to-RAM on my system has stopped working reliably on Vivid when booting with Systemd. When I try to suspend my PC the following happens: - PC turns off - PC unwantedly wakes up (turns on) by itself again. This time span until it turns on again can reach from a second (almost immediately) until two or three minutes. - In a few cases (<25%), the PC stays suspended properly. A way to workaround this problem is to boot my PC with Upstart instead of Systemd, then this problem never happens (and has never happened in any of the previous Ubuntu versions since 2008). Thus it seems to be a bug somehow related to Systemd. Other steps I have tried to solve the problem (without any success): - Checking BIOS settings, all options are set that way that the PC should never wake up by any event other than pressing the power button. - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device could cause wake up events. This lists my USB controller, but deactivating it (with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the problem. Also suspend while running Upstart works fine despite the USB controller listed as "enabled". In the system logs I could see no hint what causes the undesired wake- ups. Allthough there is one factor which seems to have a certain influence: If I close programs like Pidgin, Skype or Firefox that cause continuous network traffic, the chance is higher that my PC will stay suspened (while runinng Systemd). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 11:24:46 2015 InstallationDate: Installed on 2015-04-16 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1450396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
The current verification-done tag looks like it is intended for Yakkety only, and the Xenial proposed package still needs verification. ** Tags removed: verification-done ** Tags added: verification-done-yakkety verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Yakkety: Fix Released Status in linux-firmware source package in Zesty: Fix Committed Bug description: SRU Justification Impact: The -22 firmware for iwlwifi introduces regressions with some hardware versus earlier firmware versions. As no newer firmware is available, the only fix is to revert back to the older firmware which does work. Test Case: Using the -22 firmware with affected hardware produces the behavior described below. The -21 firmware does not. Regression Potential: Switching back to -21 could cause some regressions with other hardware supported by this firmware. However as -22 causes some hardware to completely fail to work any regressions are almost certain to be less severe than the current problems. --- The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657112] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp4__4.8.0-36.38__2017-01-25_10-40-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657112 Title: linux: 4.8.0-36.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.8.0-35.37 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1657112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial
I took the xps15 from tai. The kernel is already upgraded to 4.4.0-62. I tested it with PHILIPS 288PL6 4K monitor and cannot reproduce the issue. Connected the monitor via HDMI and Type-C (to HDMI) ports and both works well. All display modes are available. Checked dmesg and /var/log/syslog, there is no similar warning or kernel panics messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658999 Title: [Xenial Regression] Kernel panics on HDMI in Xenial Status in linux package in Ubuntu: Triaged Bug description: sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a wide range of displays. He's running 4.4.0-62.83 and notes this is definitely a regression as it was working previously. Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995791] [ cut here ] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995842] WARNING: CPU: 4 PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995846] WARN_ON(!wm_changed) Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.995849] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152 v4l2_common hid_multitouch mii videodev snd media joydev input_leds serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800 intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf industrialio kvm_intel kvm irqbypass iptable_filter ip_tables ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4 usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi pinctrl_sunrisepoint video pinctrl_intel fjes Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996021] CPU: 4 PID: 2548 Comm: Xorg Tainted: P O4.4.0-62-generic #83-Ubuntu Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996024] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996027] 0286 5b61ce69 880880293920 813f7c63 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996033] 880880293968 c02be9a0 880880293958 810812d2 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996037] 88089255f000 88089160a148 88089255e000 880892644b78 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996042] Call Trace: Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996051] [] dump_stack+0x63/0x90 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996059] [] warn_slowpath_common+0x82/0xc0 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996064] [] warn_slowpath_fmt+0x5c/0x80 Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996101] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996136] [] skl_update_wm+0x185/0x610 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996190] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996225] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996276] [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996327] [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996366] [] ? drm_atomic_check_only+0x18e/0x590 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996397] [] drm_atomic_commit+0x37/0x60 [drm] Jan 24 08:32:31 mark-XPS-15-9550 kernel: [ 489.996415] [] drm_atomic_helper_set_config+0x76/0xb0 [
[Kernel-packages] [Bug 1655878] Re: uvcvideo fails to init camera and then dmesg is full with traces
I failed to run on new kernel - I tried to run linux- image-4.10.0-041000rc4-generic_4.10.0-041000rc4.201701152031_amd64.deb and it just hangs. I also tried to remove nvidia module and failed. http://askubuntu.com/questions/875310/where-nvidia-kernel-module-is-hiding -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655878 Title: uvcvideo fails to init camera and then dmesg is full with traces Status in linux package in Ubuntu: Incomplete Bug description: The dmesg log should be attached. Camera doesn't work. It worked once when I first plugged it and run guvcview (cheese couldn't find it). Offending lines: [ 184.760036] usb 2-4: new high-speed USB device number 2 using ehci-pci [ 184.936757] usb 2-4: New USB device found, idVendor=0ac8, idProduct=3420 [ 184.936762] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 184.936765] usb 2-4: Product: Vimicro USB2.0 Camera [ 184.936768] usb 2-4: Manufacturer: Vimicro Corp. [ 185.096698] media: Linux media interface: v0.10 [ 185.137703] Linux video capture interface: v2.00 [ 236.272492] usbcore: registered new interface driver snd-usb-audio [ 236.273934] uvcvideo: Found UVC 1.00 device Vimicro USB2.0 Camera (0ac8:3420) [ 236.291047] uvcvideo 2-4:1.0: Entity type for entity Processing 2 was not initialized! [ 236.291054] uvcvideo 2-4:1.0: Entity type for entity Camera 1 was not initialized! [ 236.291057] uvcvideo 2-4:1.0: Entity type for entity Extension 4 was not initialized! [ 236.291781] input: Vimicro USB2.0 Camera as /devices/pci:00/:00:1d.7/usb2/2-4/2-4:1.0/input/input14 [ 236.303796] usbcore: registered new interface driver uvcvideo [ 236.303799] USB Video Class driver (1.1.1) [ 256.624304] usb 2-4: USB disconnect, device number 2 [ 256.648053] [ cut here ] [ 256.648063] WARNING: CPU: 1 PID: 6752 at /build/linux-RZGRu0/linux-4.8.0/fs/sysfs/group.c:237 sysfs_remove_group+0x8b/0x90 [ 256.648065] sysfs group 9c8d04a0 not found for kobject 'event14' ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: techtonik 6121 F pulseaudio /dev/snd/controlC0: techtonik 6121 F pulseaudio Date: Thu Jan 12 11:40:54 2017 HibernationDevice: RESUME=UUID=89bb43be-f25f-4caa-9f0c-7bb67d5f5583 MachineType: System manufacturer P5KR ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=8814b3f6-00a6-45a7-a112-afd933fdc5b5 ro quiet splash vt.handoff=7 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.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-20 (84 days ago) dmi.bios.date: 06/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd06/26/2008:svnSystemmanufacturer:pnP5KR:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KR:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5KR dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1659225] [NEW] juju: enable ceph-rbd configuration for nova-compute-proxy charm
Public bug reported: This is a request to support ceph-rbd as a backing store for cinder-deployed volumes and nova ephemeral disks as part of the compute proxy charm for KVM for z. When an openstack juju bundle gets deployed with a ceph cluster as a backing store for cinder(-ceph), the ceph-rbd client on KVM for z should be configured to communicate with this cinder-ceph, along with the necessary configurations in libvirt and nova to allow attachments of the ceph-rbd volumes/disks to the nova instances running on KVM for z. ---uname output--- Linux zfwcec082 4.4.0-40.60.el7_2.kvmibm1_1_3.2.s390x #1 SMP Tue Oct 18 14:41:51 EDT 2016 s390x s390x s390x GNU/Linux Machine Type = 2847-743 ---Steps to Reproduce--- 1. Deploy KVM on z via juju nova-compute-proxy charm (https://jujucharms.com/u/openstack-charmers-next/nova-compute-proxy/) along with ceph and cinder-ceph on other (Ubuntu) systems. 2. create a volume on ceph backend and attach to a nova instance running on KVM for z. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-150906 severity-critical targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-150906 severity-critical targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1659225 Title: juju: enable ceph-rbd configuration for nova-compute-proxy charm Status in linux package in Ubuntu: New Bug description: This is a request to support ceph-rbd as a backing store for cinder-deployed volumes and nova ephemeral disks as part of the compute proxy charm for KVM for z. When an openstack juju bundle gets deployed with a ceph cluster as a backing store for cinder(-ceph), the ceph-rbd client on KVM for z should be configured to communicate with this cinder-ceph, along with the necessary configurations in libvirt and nova to allow attachments of the ceph-rbd volumes/disks to the nova instances running on KVM for z. ---uname output--- Linux zfwcec082 4.4.0-40.60.el7_2.kvmibm1_1_3.2.s390x #1 SMP Tue Oct 18 14:41:51 EDT 2016 s390x s390x s390x GNU/Linux Machine Type = 2847-743 ---Steps to Reproduce--- 1. Deploy KVM on z via juju nova-compute-proxy charm (https://jujucharms.com/u/openstack-charmers-next/nova-compute-proxy/) along with ceph and cinder-ceph on other (Ubuntu) systems. 2. create a volume on ceph backend and attach to a nova instance running on KVM for z. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
