[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
@Frode, I can yes, when I file them. I need to do a bit of work for simple reproducers/etc/etc to file them. I've added an item to add a comment to this bug when I do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408106 Title: attach_disconnected not sufficient for overlayfs Status in AppArmor: Invalid Status in MAAS: Incomplete Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: With the following use of overlayfs, we get a disconnected path: $ cat ./profile #include profile foo { #include capability sys_admin, capability sys_chroot, mount, pivot_root, } $ cat ./overlay.c #include #include #include #include #include #include #include int main(int argc, char* argv[]) { int i = 0; int len = 0; int ret = 0; char* options; if (geteuid()) unshare(CLONE_NEWUSER); unshare(CLONE_NEWNS); for (i = 1; i < argc; i++) { if (i == 1) { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]); } else { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", argv[i]); } mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options); } chdir("/mnt"); pivot_root(".", "."); chroot("."); chdir("/"); execl("/bin/bash", "/bin/bash", NULL); } $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp [255] ... Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 With the above, the expectation was for the denial to be /mnt/bin/bash. There are three ways forward: 1. the correct solution is to patch overlayfs to properly track the loopback, but this will take a while, may ultimately be unachievable. UPDATE: upstream is currently working on this and Ubuntu will engage with them 2. we could rely on the fact that overlayfs creates a private unshared submount, and provide a way to not mediate the path when that is present, and tagged. This would take a bit of time, and might be the preferred method over 1 longer term 3. we could extend attach_disconnected so that we can define the attach root. Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Update: After reboot, the touchpad is not back to being completely dead (I sensed this was going to happen). Obviously it's supported since it worked flawlessly at one point so what could possibly be the problem and where to look for 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/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B:
[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
Do we know which kernel version caused the regression? If so, I can review the commits or perform a bisect if needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697395] Re: Thunderbolt devices don't work if connected during boot
Kai-Heng, did you run the command as root? Otherwise you may want to `sudo su` and run the loop or "prime" your sudo by running `sudo echo` (to get prompted for you password once) and then use the same loop but instead of `> /path/to/file` use `| tee /path/to/file` and see if you get different results. I will bookmark this to test after my next restart, as I'm seeing the same issue on boot, and I don't know that changing the system hardware test from Automatic to Thorough or Quick in the BIOS will make a difference. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697395 Title: Thunderbolt devices don't work if connected during boot Status in linux package in Ubuntu: Triaged Bug description: I am using a Dell XP 15 9550, if my Dockingstation (Dell TB16) is connected during boot time, all the USB devices (like Keyboard, Ethernet, ...) are only working while in grub boot menu. After booting they stop working. The two 4k screens which are connected to the dock, are working properly in boot menu and after booting. If booting into Windows everything is working, only linux is affected. Disconnecting and reconnecting the dock solves this problem. I have created the bug-report directly after boot, where the USB devices are not working and attached "lspci-vnvn_after_reconnect.log" after reconnecting the dock. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic 4.10.0-22.24 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre_duewel 3163 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Jun 12 11:17:26 2017 InstallationDate: Installed on 2017-04-12 (60 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=0ba04b8b-151f-4522-81a8-b6b01352ea35 ro quiet splash nvme_core.default_ps_max_latency_us=6000 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702521] Comment bridged from LTC Bugzilla
--- Comment From ukri...@us.ibm.com 2017-07-06 14:07 EDT--- Victor, I verified the patched kernel from the given location. It passes the basic FVT test. Thanks for the quick turnaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702521 Title: cxlflash update request in the Xenial SRU stream Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Request to update cxlflash in the Xenial SRU stream There are multiple patches in upstream that are of interest and would like to see them pulled into the Xenial SRU stream. I have listed the patches that are in upstream/master tree. 41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when destroying context 44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter within context 888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to application close model de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file descriptor cache 9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context reference tracking on detach 68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 1 instead of SG_NONE 8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in cxlflash_restore_luntable() 3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve context_reset() logic 11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room violation e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer from AFU command 350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory instead of using command pool for AFU sync 5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for private commands 25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private command pool de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU commands to timeout upon tear down 9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command lock d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf() 9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup queuecommand() 48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN specific routines to function pointers fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command pointer to AFU command 9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context reset to share reset logic 696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command Mode fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints 0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled workers before stopping AFU 943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID for future IBM CXL Flash AFU 76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ processing from the RRQ interrupt handler f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access and support offlevel processing cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ polling for RRQ processing 3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper routines to pass config structure 78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic number of FC ports 8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port configuration assumptions 0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals behind common access routine 565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to support 4 ports 1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports 323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during probe 50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary DMA mapping cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two validations fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous interrupt processing bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple hardware queues 3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues attribute 1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware queue
[Kernel-packages] [Bug 1676635] Re: [Hyper-V] Implement Hyper-V PTP Source
Hi Marcelo, I kicked the tires on 4.4.0-85-generic kernel from xenial-proposed. The fixes look good. I see the PTP device and TimeSync is not causing "Time has been changed" messages in systemd. I also see that apt-daily timer is no longer being randomly delayed due to the clock 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/1676635 Title: [Hyper-V] Implement Hyper-V PTP Source Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Please include the following upstream commit into lts-xenial, 16.04 HWE, Yakkity, and Zesty. This will improve the behavior of timesync on Hyper-V hosts while simultaneously using network time sync protocols like NTP. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/hv_util.c?id=3716a49a81ba19dda7202633a68b28564ba95eb5 commit 3716a49a81ba19dda7202633a68b28564ba95eb5 Author: Vitaly KuznetsovDate: Sat Feb 4 09:57:14 2017 -0700 hv_utils: implement Hyper-V PTP source With TimeSync version 4 protocol support we started updating system time continuously through the whole lifetime of Hyper-V guests. Every 5 seconds there is a time sample from the host which triggers do_settimeofday[64](). While the time from the host is very accurate such adjustments may cause issues: - Time is jumping forward and backward, some applications may misbehave. - In case an NTP server runs in parallel and uses something else for time sync (network, PTP,...) system time will never converge. - Systemd starts annoying you by printing "Time has been changed" every 5 seconds to the system log. Instead of doing in-kernel time adjustments offload the work to an NTP client by exposing TimeSync messages as a PTP device. Users may now decide what they want to use as a source. I tested the solution with chrony, the config was: refclock PHC /dev/ptp0 poll 3 dpoll -2 offset 0 The result I'm seeing is accurate enough, the time delta between the guest and the host is almost always within [-10us, +10us], the in-kernel solution was giving us comparable results. I also tried implementing PPS device instead of PTP by using not currently used Hyper-V synthetic timers (we use only one of four for clockevent) but with PPS source only chrony wasn't able to give me the required accuracy, the delta often more that 100us. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan Signed-off-by: Greg Kroah-Hartman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
@Frode, Users running 2.2 *already* have the apparmor=0 work around for *ephemeral* environments only. For users running previous versions, we recommend you upgrade immediately, provided that 2.0 and 2.1 are out of support. If you decide not to upgrade, your options are: 1. Use a HWE kernel (such as hwe-16.04). https://bugs.launchpad.net/cloud-init/+bug/1701297/comments/21 2. Use apparmor=0 as a global/machine kernel param (this will result in the deployed machine with apparmor disabled) Marking this invalid for MAAS provided the bug is overlayfs. ** Changed in: maas Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408106 Title: attach_disconnected not sufficient for overlayfs Status in AppArmor: Invalid Status in MAAS: Invalid Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: With the following use of overlayfs, we get a disconnected path: $ cat ./profile #include profile foo { #include capability sys_admin, capability sys_chroot, mount, pivot_root, } $ cat ./overlay.c #include #include #include #include #include #include #include int main(int argc, char* argv[]) { int i = 0; int len = 0; int ret = 0; char* options; if (geteuid()) unshare(CLONE_NEWUSER); unshare(CLONE_NEWNS); for (i = 1; i < argc; i++) { if (i == 1) { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]); } else { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", argv[i]); } mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options); } chdir("/mnt"); pivot_root(".", "."); chroot("."); chdir("/"); execl("/bin/bash", "/bin/bash", NULL); } $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp [255] ... Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 With the above, the expectation was for the denial to be /mnt/bin/bash. There are three ways forward: 1. the correct solution is to patch overlayfs to properly track the loopback, but this will take a while, may ultimately be unachievable. UPDATE: upstream is currently working on this and Ubuntu will engage with them 2. we could rely on the fact that overlayfs creates a private unshared submount, and provide a way to not mediate the path when that is present, and tagged. This would take a bit of time, and might be the preferred method over 1 longer term 3. we could extend attach_disconnected so that we can define the attach root. Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702768] [NEW] Ubuntu 17.04 KVM: stack trace generated when enabling SRIOV in power
Public bug reported: ---Problem Description--- When enabling SRIOV with kernel 4.10.0-26-generic in power will see this stack trace: [ 2084.079575] [ cut here ] [ 2084.079583] WARNING: CPU: 120 PID: 734 at /build/linux-TAhFXm/linux-4.10.0/arch/powerpc/platforms/powernv/npu-dma.c:78 pnv_pci_get_npu_dev+0x40/0xb0 [ 2084.079584] Modules linked in: mst_pciconf(OE) mst_pci(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) ib_ipoib(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) binfmt_misc bridge stp llc ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng powernv_op_panel uio_pdrv_genirq leds_powernv uio ibmpowernv vmx_crypto sunrpc ib_iser(OE) rdma_cm(OE) iw_cm(OE) ib_cm(OE) ib_core(OE) configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx [ 2084.079640] xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_en(OE) ses enclosure scsi_transport_sas crc32c_vpmsum tg3 mlx5_core(OE) mlx4_core(OE) ipr devlink mlx_compat(OE) [ 2084.079658] CPU: 120 PID: 734 Comm: kworker/120:0 Tainted: GW OE 4.10.0-26-generic #30-Ubuntu [ 2084.079663] Workqueue: events work_for_cpu_fn [ 2084.079665] task: c00fee60dc00 task.stack: c00fee534000 [ 2084.079666] NIP: c009c210 LR: c009d404 CTR: [ 2084.079668] REGS: c00fee537700 TRAP: 0700 Tainted: GW OE (4.10.0-26-generic) [ 2084.079669] MSR: 9282b033[ 2084.079677] CR: 42004428 XER: 2000 [ 2084.079678] CFAR: c009d400 SOFTE: 1 GPR00: c009d404 c00fee537980 c145d100 GPR04: 0aa6 c01fff70 00049188 GPR08: 0007 0001 0001 GPR12: 2200 cfbc3800 c010ef48 c00ff70ec540 GPR16: c00ffa622c58 c00ffa622a10 c00ffa6229a0 0001 GPR20: c1318de8 c0d700e8 0001 GPR24: c0d6f070 c0d6f050 c3d02000 c3d02098 GPR28: c00e92680060 081f [ 2084.079702] NIP [c009c210] pnv_pci_get_npu_dev+0x40/0xb0 [ 2084.079704] LR [c009d404] pnv_npu_try_dma_set_bypass+0x144/0x250 [ 2084.079705] Call Trace: [ 2084.079708] [c00fee5379b0] [c009d404] pnv_npu_try_dma_set_bypass+0x144/0x250 [ 2084.079710] [c00fee537a80] [c0096c74] pnv_pci_ioda_dma_set_mask+0xa4/0x150 [ 2084.079714] [c00fee537b00] [c00291a0] dma_set_mask+0x40/0xc0 [ 2084.079728] [c00fee537b20] [d000143531e4] init_one+0x33c/0x6a0 [mlx5_core] [ 2084.079732] [c00fee537bd0] [c066ba9c] local_pci_probe+0x6c/0x140 [ 2084.079734] [c00fee537c60] [c01016b8] work_for_cpu_fn+0x38/0x60 [ 2084.079737] [c00fee537c90] [c01061a0] process_one_work+0x2b0/0x5a0 [ 2084.079740] [c00fee537d20] [c0106780] worker_thread+0x2f0/0x650 [ 2084.079742] [c00fee537dc0] [c010f0a4] kthread+0x164/0x1b0 [ 2084.079746] [c00fee537e30] [c000b4e8] ret_from_kernel_thread+0x5c/0x74 [ 2084.079747] Instruction dump: [ 2084.079748] 7c0802a6 fbe1fff8 f8010010 f821ffd1 7c690074 7929d182 0b09 2fa3 [ 2084.079753] 419e0060 e8630330 7c690074 7929d182 <0b09> 2fa3 419e0048 7c852378 [ 2084.079759] ---[ end trace 7bf01a937efd69d8 ]--- This issue was introduced by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c3b89effc281704d5395282c800c45e453235f6 (Subject: powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev ) and the solution will be to add this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=377aa6b0efbaa29cfeecd8b9244641217f9544ca which reads: "powerpc/npu-dma: Remove spurious WARN_ON when a PCI device has no of_node" Requesting fix inclusion in 17.04 and probably 16.04.3. ---uname output--- 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:29:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Need a Mellanox card that supports SRIOV. Machine Type = P8 ---Steps to Reproduce--- Just enable SRIOV in a power system with Mellanox CX4 or CX5 will be like this: echo 1 > /sys/class/infiniband/mlx5_0/device/sriov_numvfs Stack trace output: [ 2084.079567] mlx5_core 0004:01:04.0: Using 64-bit DMA iommu bypass [ 2084.079575] [ cut here ] [
[Kernel-packages] [Bug 1702768] [NEW] Ubuntu 17.04 KVM: stack trace generated when enabling SRIOV in power
You have been subscribed to a public bug: ---Problem Description--- When enabling SRIOV with kernel 4.10.0-26-generic in power will see this stack trace: [ 2084.079575] [ cut here ] [ 2084.079583] WARNING: CPU: 120 PID: 734 at /build/linux-TAhFXm/linux-4.10.0/arch/powerpc/platforms/powernv/npu-dma.c:78 pnv_pci_get_npu_dev+0x40/0xb0 [ 2084.079584] Modules linked in: mst_pciconf(OE) mst_pci(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rdma_ucm(OE) ib_ucm(OE) ib_ipoib(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) binfmt_misc bridge stp llc ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng powernv_op_panel uio_pdrv_genirq leds_powernv uio ibmpowernv vmx_crypto sunrpc ib_iser(OE) rdma_cm(OE) iw_cm(OE) ib_cm(OE) ib_core(OE) configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx [ 2084.079640] xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_en(OE) ses enclosure scsi_transport_sas crc32c_vpmsum tg3 mlx5_core(OE) mlx4_core(OE) ipr devlink mlx_compat(OE) [ 2084.079658] CPU: 120 PID: 734 Comm: kworker/120:0 Tainted: GW OE 4.10.0-26-generic #30-Ubuntu [ 2084.079663] Workqueue: events work_for_cpu_fn [ 2084.079665] task: c00fee60dc00 task.stack: c00fee534000 [ 2084.079666] NIP: c009c210 LR: c009d404 CTR: [ 2084.079668] REGS: c00fee537700 TRAP: 0700 Tainted: GW OE (4.10.0-26-generic) [ 2084.079669] MSR: 9282b033[ 2084.079677] CR: 42004428 XER: 2000 [ 2084.079678] CFAR: c009d400 SOFTE: 1 GPR00: c009d404 c00fee537980 c145d100 GPR04: 0aa6 c01fff70 00049188 GPR08: 0007 0001 0001 GPR12: 2200 cfbc3800 c010ef48 c00ff70ec540 GPR16: c00ffa622c58 c00ffa622a10 c00ffa6229a0 0001 GPR20: c1318de8 c0d700e8 0001 GPR24: c0d6f070 c0d6f050 c3d02000 c3d02098 GPR28: c00e92680060 081f [ 2084.079702] NIP [c009c210] pnv_pci_get_npu_dev+0x40/0xb0 [ 2084.079704] LR [c009d404] pnv_npu_try_dma_set_bypass+0x144/0x250 [ 2084.079705] Call Trace: [ 2084.079708] [c00fee5379b0] [c009d404] pnv_npu_try_dma_set_bypass+0x144/0x250 [ 2084.079710] [c00fee537a80] [c0096c74] pnv_pci_ioda_dma_set_mask+0xa4/0x150 [ 2084.079714] [c00fee537b00] [c00291a0] dma_set_mask+0x40/0xc0 [ 2084.079728] [c00fee537b20] [d000143531e4] init_one+0x33c/0x6a0 [mlx5_core] [ 2084.079732] [c00fee537bd0] [c066ba9c] local_pci_probe+0x6c/0x140 [ 2084.079734] [c00fee537c60] [c01016b8] work_for_cpu_fn+0x38/0x60 [ 2084.079737] [c00fee537c90] [c01061a0] process_one_work+0x2b0/0x5a0 [ 2084.079740] [c00fee537d20] [c0106780] worker_thread+0x2f0/0x650 [ 2084.079742] [c00fee537dc0] [c010f0a4] kthread+0x164/0x1b0 [ 2084.079746] [c00fee537e30] [c000b4e8] ret_from_kernel_thread+0x5c/0x74 [ 2084.079747] Instruction dump: [ 2084.079748] 7c0802a6 fbe1fff8 f8010010 f821ffd1 7c690074 7929d182 0b09 2fa3 [ 2084.079753] 419e0060 e8630330 7c690074 7929d182 <0b09> 2fa3 419e0048 7c852378 [ 2084.079759] ---[ end trace 7bf01a937efd69d8 ]--- This issue was introduced by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c3b89effc281704d5395282c800c45e453235f6 (Subject: powerpc/powernv: Add sanity checks to pnv_pci_get_{gpu|npu}_dev ) and the solution will be to add this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=377aa6b0efbaa29cfeecd8b9244641217f9544ca which reads: "powerpc/npu-dma: Remove spurious WARN_ON when a PCI device has no of_node" Requesting fix inclusion in 17.04 and probably 16.04.3. ---uname output--- 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:29:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Need a Mellanox card that supports SRIOV. Machine Type = P8 ---Steps to Reproduce--- Just enable SRIOV in a power system with Mellanox CX4 or CX5 will be like this: echo 1 > /sys/class/infiniband/mlx5_0/device/sriov_numvfs Stack trace output: [ 2084.079567] mlx5_core 0004:01:04.0: Using 64-bit DMA iommu bypass [ 2084.079575] [ cut
[Kernel-packages] [Bug 1701857] Re: Kernel Oops - unable to handle kernel paging request; RIP: 0010:[] [] fput+0x5/0x90
I first noticed the problem on kernel 4.4.0-81. The computer froze up a few times before I started digging into the logs to try and figure out what was wrong. It was freezing about 3-4 times per day. I rolled back to kernel 4.4.0-79, which seemed to be more stable but still suffered an Oops at least once per day. Upgraded to 4.4.0-83 when it became available, but still suffering an Oops occasionally. Also around this time I was suffering graphics issues where the display became unresponsive. There was no kernel oops, but it seemed the nouveau driver was crashing. I've switched to the nvidia proprietry driver, which has resulted in a stable display, but even since then a kernel oops reoccured. Most recent log of the oops below. I'm probably not too keen to go mainline kernel as this is not a testing system - but could we achieve a similar test if I went for the HWE kernel (which I think is currently 4.8 ?) Thank you for your reply! Jul 6 11:07:42 Ultimate kernel: [56740.260384] BUG: unable to handle kernel paging request at 8802ddeb2db8 Jul 6 11:07:42 Ultimate kernel: [56740.260451] IP: [] vma_interval_tree_insert+0x26/0x80 Jul 6 11:07:42 Ultimate kernel: [56740.260515] PGD 1020c067 PUD 0 Jul 6 11:07:42 Ultimate kernel: [56740.260544] Oops: [#1] SMP Jul 6 11:07:42 Ultimate kernel: [56740.260575] Modules linked in: nls_utf8 isofs scsi_transport_iscsi nvram msr ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter aufs binfmt_misc veth pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc iptable_filter ip_tables x_tables snd_usb_audio snd_usbmidi_lib input_leds joydev gspca_zc3xx gspca_main v4l2_common videodev media nvidia_uvm(POE) snd_hda_codec_hdmi nvidia(POE) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd serio_raw snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer snd shpchp soundcore mei_me mei lpc_ich 8250_fintek mac_hid parport_pc pp dev lp parport autofs4 hid_generic psmouse uas i915 firewire_ohci firewire_core crc_itu_t pata_acpi usb_storage usbhid i2c_algo_bit hid r8169 mii drm_kms_helper syscopyarea sysfillrect video sysimgblt fb_sys_fops fjes drm Jul 6 11:07:42 Ultimate kernel: [56740.260734] CPU: 0 PID: 28425 Comm: systemd-cgroups Tainted: P OE 4.4.0-83-generic #106-Ubuntu Jul 6 11:07:42 Ultimate kernel: [56740.260735] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H61M-S2PV, BIOS FE 06/21/2012 Jul 6 11:07:42 Ultimate kernel: [56740.260737] task: 88029dd0ce00 ti: 88029fbd task.ti: 88029fbd Jul 6 11:07:42 Ultimate kernel: [56740.260738] RIP: 0010:[] [] vma_interval_tree_insert+0x26/0x80 Jul 6 11:07:42 Ultimate kernel: [56740.260741] RSP: 0018:88029fbd3d40 EFLAGS: 00010286 Jul 6 11:07:42 Ultimate kernel: [56740.260742] RAX: 8802ddeb2da0 RBX: 88029eb99400 RCX: Jul 6 11:07:42 Ultimate kernel: [56740.260743] RDX: 8802a2579b90 RSI: 8802a2579b90 RDI: 8802a231d320 Jul 6 11:07:42 Ultimate kernel: [56740.260744] RBP: 88029fbd3d48 R08: 021c R09: Jul 6 11:07:42 Ultimate kernel: [56740.260746] R10: 8802a231d320 R11: 0021e000 R12: 8802a231d320 Jul 6 11:07:42 Ultimate kernel: [56740.260747] R13: 88008fa337f0 R14: 88008fa33800 R15: 8802a2579b98 Jul 6 11:07:42 Ultimate kernel: [56740.260748] FS: () GS:8802af20() knlGS: Jul 6 11:07:42 Ultimate kernel: [56740.260750] CS: 0010 DS: ES: CR0: 80050033 Jul 6 11:07:42 Ultimate kernel: [56740.260751] CR2: 8802ddeb2db8 CR3: 0002481df000 CR4: 000406f0 Jul 6 11:07:42 Ultimate kernel: [56740.260751] Stack: Jul 6 11:07:42 Ultimate kernel: [56740.260752] 811c6636 88029fbd3d90 811c71e4 88009086e4b0 Jul 6 11:07:42 Ultimate kernel: [56740.260754] 8802a2579b70 88008fa33800 7f651ac33000 0075 Jul 6 11:07:42 Ultimate kernel: [56740.260756] 88009086e4b0 8802a231d320 88029fbd3e20 811c96fb Jul 6 11:07:42 Ultimate kernel: [56740.260759] Call Trace: Jul 6 11:07:42 Ultimate kernel: [56740.260762] [] ? __vma_link_file+0x46/0x50 Jul 6 11:07:42 Ultimate kernel: [56740.260765] [] vma_link+0x74/0xc0 Jul 6 11:07:42 Ultimate kernel: [56740.260767] [] mmap_region+0x41b/0x650 Jul 6 11:07:42 Ultimate kernel: [56740.260770] [] do_mmap+0x333/0x420 Jul 6 11:07:42 Ultimate kernel: [56740.260774] [] vm_mmap_pgoff+0xaf/0xe0 Jul 6 11:07:42 Ultimate kernel: [56740.260776] [] SyS_mmap_pgoff+0x1c1/0x290 Jul 6 11:07:42
[Kernel-packages] [Bug 1702749] Re: arm64: fix crash reading /proc/kcore
** Description changed: [Impact] Reading /proc/kcore can lead to a crash on arm64 systems. + This was found to cause crashes when, e.g. annotating symbols in a perf top session. [Test Case] # cat /proc/kcore > /dev/null [Regression Risk] + 2 upstream patches need to be cherry-picked to fix this. + + The 1st patch is a simplification to the kcore driver that impacts all + architectures. Instead of re-checking at read time for vmalloc/module + addresses, it just checks for a flag that was set during kcore driver + init. This looks correct to me but could of course have an unnoticed + bug. + + The second patch is arm64-specific, and regression risk has been + mitigated by testing on arm64 hardware. ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Zesty) 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/1702749 Title: arm64: fix crash reading /proc/kcore Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: [Impact] Reading /proc/kcore can lead to a crash on arm64 systems. This was found to cause crashes when, e.g. annotating symbols in a perf top session. [Test Case] # cat /proc/kcore > /dev/null [Regression Risk] 2 upstream patches need to be cherry-picked to fix this. The 1st patch is a simplification to the kcore driver that impacts all architectures. Instead of re-checking at read time for vmalloc/module addresses, it just checks for a flag that was set during kcore driver init. This looks correct to me but could of course have an unnoticed bug. The second patch is arm64-specific, and regression risk has been mitigated by testing on arm64 hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Was this issue officially confirmed to be a hardware bug in Ryzen processors by AMD? If so, could you provide a link to the statement? Disabling address space layout randomization (ASLR) seems to alleviate the problem, but does it solve it? I am investigating unstable behavior under load which could be related. There, disabling ASLR is not sufficient! People suggest to increase SOC voltages, use specific versions of the kernel and the like. See https://community.amd.com/thread/215773?start=135=0 for more info. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1701182] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** 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/1701182 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: software center keeps stalling on OS package updates - been failing for some time - the last time I circumvented it, I had to re-install Software Center using a terminal - that's all I got ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gerry 1608 F pulseaudio /dev/snd/controlC1: gerry 1608 F pulseaudio Date: Thu Jun 29 00:36:36 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=efe70c28-f88a-4598-8c7c-12f01ef03eb9 InstallationDate: Installed on 2016-08-28 (304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=de48053a-b75a-4b32-9131-5455a8677d28 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.38 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F2 dmi.board.vendor: Quanta dmi.board.version: 98.36 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.38:bd11/11/2009:svnHewlett-Packard:pnHPPaviliondv5NotebookPC:pvrRev1:rvnQuanta:rn30F2:rvr98.36:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv5 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627828] Re: iwl3945 crashes randomly
A second HP 6710b has wifi that still works. I have not tried an update. matthew@matthew-HP-Compaq-6710b-GB898ET-ABU:~$ uname -rsvp Linux 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627828 Title: iwl3945 crashes randomly Status in linux package in Ubuntu: Confirmed Bug description: Out of nothing a once properly working 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) started to crash with: Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320032] iwl3945 :0c:00.0: Error sending C_POWER_TBL: time out after 500ms. Sep 22 14:38:16 seba-Latitude-D630 kernel: [26707.320039] iwl3945 :0c:00.0: set power fail, ret = -110 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012031] iwl3945 :0c:00.0: Queue 2 stuck for 2500 ms. Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.012039] iwl3945 :0c:00.0: On demand firmware reload Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.050333] ieee80211 phy0: Hardware restart was requested Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.084769] retire_capture_urb: 33 callbacks suppressed Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098359] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.098364] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145087] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.145089] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191802] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.191805] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238526] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.238528] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285272] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.285275] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 Sep 22 14:38:17 seba-Latitude-D630 kernel: [26708.322030] iwl3945 :0c:00.0: Unable to initialize device after 5 attempts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seba 1421 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Sep 26 16:38:18 2016 HibernationDevice: RESUME=UUID=64d7608d-53a8-46a6-884c-0ccf1814fb03 InstallationDate: Installed on 2016-08-28 (29 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude D630 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=dce979b5-6a44-48cf-a87a-d314263a895c ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701085] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Bear in mind that this bug report is only of a symptom of the real bug, which is gnome-software hanging during an update (which it seems to do regularly). So doing the install and update as explained above fixes the symptom, but not the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701085 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: The updated started and kept running for more than 30 minutes without any activity at all. It just halted. When I reboot the computer I got the error message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1601 F pulseaudio Date: Wed Jun 28 17:45:42 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=b15ac561-1f43-439b-acd7-864235fec616 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=56a7e809-b250-4de5-b5be-a9dd24718f75 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.05 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.05:bd03/01/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt
Yes, I restored last kernel on another VM, and it worked fine But panic just removed after kernel crashed, and server rebooted by itself 3 times. it's up since 2 days with crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702164 Title: Kernel panic - not syncing: Fatal exception in interrupt Status in linux package in Ubuntu: Confirmed Bug description: we updated Kernel of Ubuntu 16.04 from 4.4.0-81-generic to generic_4.4.0-83.106 we had multiple reboots, and below appeared during the boot : [231489.162816] Kernel panic - not syncing: Fatal exception in interrupt [231490.197513] Shutting down cpus with NMI [231490.210772] Kernel Offset: disabled [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-83-generic (buildd@lgw01-29) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 (Ubuntu 4.4.0-83.106-generic 4.4.70) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=e675b47c-3493-4ef8-8b6f-44acb3d1adb9 ro net.ifnames=0 biosdevname=0 cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7fff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00f47fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0xf48 max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbc20-0x000fbc2f] mapped at [880fbc20] [0.00] Scanning 1 areas for low memory corruption [0.00] Using GB pages for direct mapping [0.00] RAMDISK: [mem 0x3612a000-0x3708cfff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC014140 5C (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC0131A0 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC001CE0 011438 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC001CA0 40 [0.00] ACPI: FACS 0xFC001CA0 40 [0.00] ACPI: APIC 0xFC0132A0 000460 (v02 XenHVM HVML ) [0.00] ACPI: SRAT 0xFC013780 0008A8 (v01 XenHVM HVML ) [0.00] ACPI: HPET 0xFC014050 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC014090 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC0140C0 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC014100 31 (v02 XenHVM INTL 20090123) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 3 08:14 seq crw-rw 1 root audio 116, 33 Jul 3 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64
Re: [Kernel-packages] [Bug 1701227] Re: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Confirmed On 06/07/17 01:05, Joseph Salisbury wrote: > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" > > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Low > > ** 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/1701227 Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Update hung halfway thru on install pop up reports errors installing kernel etc ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: main 1478 F pulseaudio /dev/snd/controlC0: main 1478 F pulseaudio Date: Thu Jun 29 10:33:29 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=f5f88dc3-771e-496b-8a3d-07b1018f5035 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.213:bd10/12/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1614789] Re: zfs.target should not require zfs-share.service
** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1614789 Title: zfs.target should not require zfs-share.service Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Bug description: == SRU Xenial == [Justification] Currently package zfsutils-linux contains systemd target file /lib/systemd/system/zfs.target that specifies following dependencies: Requires=zfs-mount.service Requires=zfs-share.service Wants=zed.service zfs-share.service is not essential in setups where file sharing is not used, or when it is configured without the use of the zfs utility. The user may therefore choose to mask this service. However, doing so has an unexpected and confusing effect, preventing zfs from starting on boot at all. This is because zfs.target is the only zfs-related unit that is wanted by multi-user.target, and if one of its required services is masked, zfs.target is skipped, together with zfs- mount.service. A solution is to replace "Requires=zfs-share.service" with "Wants=zfs-share.service". [Testcase] Steps to reproduce: systemctl mask zfs-share.service reboot Expected results: Module zfs is loaded zfs-mount.service is active and ZFS filesystems are mounted ZFS filesystems are not shared Observed results: Module zfs is not loaded ZFS filesystems are not mounted zpool status produces an error: "The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them." With the fix, the modules are loaded and zfs filesystems are mounted [Fix] A solution is to replace "Requires=zfs-share.service" with "Wants=zfs-share.service". [Regression Potential] Minimal, this affects the start up of a service that should be starting and currently isn't. Limited to just this specific scenario. - $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408106] Re: attach_disconnected not sufficient for overlayfs
This problem has surfaced again with recent MAAS Ubuntu images. One report in bug 1701297. I have information about at least two other end users hit by the problem. Adding a workaround by setting apparmor=0 kernel parameter in MAAS 2.2 will not help users that are running previous versions. @jdstrand Would you care to reference the other bugs you created from your investigation? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408106 Title: attach_disconnected not sufficient for overlayfs Status in AppArmor: Invalid Status in MAAS: Incomplete Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: With the following use of overlayfs, we get a disconnected path: $ cat ./profile #include profile foo { #include capability sys_admin, capability sys_chroot, mount, pivot_root, } $ cat ./overlay.c #include #include #include #include #include #include #include int main(int argc, char* argv[]) { int i = 0; int len = 0; int ret = 0; char* options; if (geteuid()) unshare(CLONE_NEWUSER); unshare(CLONE_NEWNS); for (i = 1; i < argc; i++) { if (i == 1) { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]); } else { len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2; options = alloca(len); ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", argv[i]); } mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options); } chdir("/mnt"); pivot_root(".", "."); chroot("."); chdir("/"); execl("/bin/bash", "/bin/bash", NULL); } $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp [255] ... Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 With the above, the expectation was for the denial to be /mnt/bin/bash. There are three ways forward: 1. the correct solution is to patch overlayfs to properly track the loopback, but this will take a while, may ultimately be unachievable. UPDATE: upstream is currently working on this and Ubuntu will engage with them 2. we could rely on the fact that overlayfs creates a private unshared submount, and provide a way to not mediate the path when that is present, and tagged. This would take a bit of time, and might be the preferred method over 1 longer term 3. we could extend attach_disconnected so that we can define the attach root. Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1408106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted
The commit has been landed to mainline at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/apm?id=8aba8474181070a30f56ffd19359f5d80665175e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693673 Title: Ubuntu 16.04 IOB Error when the Mustang board rebooted Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Triaged Bug description: When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 3.07.09, the following warning messages are displayed: [ 38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction error [ 38.199164] xgene-edac 7880.edac: IOB BA write response error [ 38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. (0x) [ 38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722 This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 26 12:21 seq crw-rw 1 root audio 116, 33 May 26 12:21 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f8faea1d-17bf-4c48-9b44-ca04875978b9 IwConfig: Error: [Errno 2] No such file or directory Lsusb: 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 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AppliedMicro X-Gene Mustang Board Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-53-generic N/A linux-backports-modules-4.8.0-53-generic N/A linux-firmware1.157.10 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.8.0-53-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: Feb 28 2017 dmi.bios.vendor: AppliedMicro dmi.bios.version: 3.07.09 dmi.board.asset.tag: Not Specified dmi.board.name: X-Gene Mustang Board dmi.board.vendor: AppliedMicro dmi.board.version: 1.0 dmi.chassis.asset.tag: Not Specified dmi.chassis.type: 23 dmi.chassis.vendor: AppliedMicro dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0: dmi.product.name: X-Gene Mustang Board dmi.product.version: 1.0 dmi.sys.vendor: AppliedMicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693673/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt
sorry: it's up since 2 days without crashes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702164 Title: Kernel panic - not syncing: Fatal exception in interrupt Status in linux package in Ubuntu: Confirmed Bug description: we updated Kernel of Ubuntu 16.04 from 4.4.0-81-generic to generic_4.4.0-83.106 we had multiple reboots, and below appeared during the boot : [231489.162816] Kernel panic - not syncing: Fatal exception in interrupt [231490.197513] Shutting down cpus with NMI [231490.210772] Kernel Offset: disabled [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.4.0-83-generic (buildd@lgw01-29) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 (Ubuntu 4.4.0-83.106-generic 4.4.70) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=e675b47c-3493-4ef8-8b6f-44acb3d1adb9 ro net.ifnames=0 biosdevname=0 cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7fff] usable [0.00] BIOS-e820: [mem 0xfc00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00f47fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] Hypervisor detected: Xen [0.00] Xen version 4.2. [0.00] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs. [0.00] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks. [0.00] You might have to change the root device [0.00] from /dev/hd[a-d] to /dev/xvd[a-d] [0.00] in your root= kernel command line option [0.00] e820: last_pfn = 0xf48 max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fbc20-0x000fbc2f] mapped at [880fbc20] [0.00] Scanning 1 areas for low memory corruption [0.00] Using GB pages for direct mapping [0.00] RAMDISK: [mem 0x3612a000-0x3708cfff] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen ) [0.00] ACPI: XSDT 0xFC014140 5C (v01 XenHVM HVML ) [0.00] ACPI: FACP 0xFC0131A0 F4 (v04 XenHVM HVML ) [0.00] ACPI: DSDT 0xFC001CE0 011438 (v02 XenHVM INTL 20090123) [0.00] ACPI: FACS 0xFC001CA0 40 [0.00] ACPI: FACS 0xFC001CA0 40 [0.00] ACPI: APIC 0xFC0132A0 000460 (v02 XenHVM HVML ) [0.00] ACPI: SRAT 0xFC013780 0008A8 (v01 XenHVM HVML ) [0.00] ACPI: HPET 0xFC014050 38 (v01 XenHVM HVML ) [0.00] ACPI: WAET 0xFC014090 28 (v01 XenHVM HVML ) [0.00] ACPI: SSDT 0xFC0140C0 31 (v02 XenHVM INTL 20090123) [0.00] ACPI: SSDT 0xFC014100 31 (v02 XenHVM INTL 20090123) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 3 08:14 seq crw-rw 1 root audio 116, 33 Jul 3 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
[Kernel-packages] [Bug 1693440] Re: Cypress PS/2 Trackpad not working
Yes, it works on Windows 8 and Windows 10. Any fix for 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/1693440 Title: Cypress PS/2 Trackpad not working Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 17.04 on my laptop and found the trackpad is not working. I can make it work after running commands below. But it won`t work after reboot, I have to run the commands again to make it work. The two-finger scrolling is not working also, even with commands below. Any fix to this issue? sudo modprobe -r psmouse sudo modprobe psmouse proto=imps ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.10.0-21-generic. ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: austinchan 1208 F...m pulseaudio /dev/snd/controlC0: austinchan 1208 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9141 irq 313' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,1bab1510,00100203 HDA:80862883,80860101,0010' Controls : 37 Simple ctrls : 13 CurrentDesktop: LXDE Date: Thu May 25 15:36:51 2017 HibernationDevice: RESUME=UUID=ba951d4d-94f7-40e9-a9c4-bb371c905cb9 InstallationDate: Installed on 2017-05-21 (3 days ago) InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. Bus 001 Device 008: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 001 Device 002: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LYZPIN SL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=883b511c-a36b-4c81-abe7-467e4c5421e6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-21-generic N/A linux-backports-modules-4.10.0-21-generic N/A linux-firmware 1.164.1 RfKill: 7: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 22.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: SL dmi.board.vendor: LYZPIN dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LYZPIN dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr22.16:bd07/29/2015:svnLYZPIN:pnSL:pvrType1-TBDbyOEM:rvnLYZPIN:rnSL:rvrType2-BoardVersion:cvnLYZPIN:ct10:cvrChassisVersion: dmi.product.name: SL dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LYZPIN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700968] Re: linux 4.8.0-58.63 ADT test failure with linux 4.8.0-58.63
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700968 Title: linux 4.8.0-58.63 ADT test failure with linux 4.8.0-58.63 Status in linux package in Ubuntu: Fix Released Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/l/linux/20170628_112023_1dbab@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend
A workaround for my gvim-based hang is to not have gvim open on the sshfs when I suspend. I don't have that option with gsd-housekeeping, so I basically have to unmount sshfs before suspend, which breaks everything else (eg. open bash prompts). Using "sshfs -o reconnect" works fine except for this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702368 Title: Mounted sshfs filesystems sometimes prevent suspend Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in sshfs-fuse package in Ubuntu: New Bug description: Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a file on an sshfs filesystem. Sometimes when I suspend I get: Jul 4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done. Jul 4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep (mem) Jul 4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... Jul 4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): Jul 4 20:59:08 xps kernel: [46704.620534] gvimD0 11155 1336 0x0004 Jul 4 20:59:08 xps kernel: [46704.620541] Call Trace: Jul 4 20:59:08 xps kernel: [46704.620556] __schedule+0x233/0x6f0 ... Jul 4 20:59:08 xps kernel: [46704.620679] entry_SYSCALL_64_fastpath+0x1e/0xad ... Jul 4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done. ...and the system fails to suspend. AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an extensive explanation. The corresponding Debian bug was closed long ago due to inactivity. It isn't exactly bug 388419 though since that is about behaviour after resume, rather than failure to suspend. This affects sshfs-fuse, but it sounds like a full fix would be in the kernel. I wonder if it's possible to work around in userspace packaging in sshfs-fuse, though, by arranging some action in userspace before suspend? It seems unlikely that this will be addressed any time soon, but it'd be nice to keep a bug open in Launchpad so that users can have a single rallying point. --- ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 1519 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: sshfs-fuse ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 Tags: artful Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+subscriptions -- Mailing list: https://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 1701227] Re: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Hi Joseph I have a script that runs the commands you suggest Not only was this a fresh install but I have flickering icons from time to time ! Appears this standalone install may have some more bugs beside this one ! Thanks Raoul On 06/07/17 01:05, Joseph Salisbury wrote: > You may need to run the following from a terminal: > > sudo apt-get install -f > sudo apt-get clean > sudo apt-get update > > Then re-install the package or updates. > > If that does not resolve your issue, please mark the bug as "Confirmed" > > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Low > > ** 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/1701227 Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Update hung halfway thru on install pop up reports errors installing kernel etc ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: main 1478 F pulseaudio /dev/snd/controlC0: main 1478 F pulseaudio Date: Thu Jun 29 10:33:29 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=f5f88dc3-771e-496b-8a3d-07b1018f5035 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.213:bd10/12/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend
I'm also hitting this with: Jul 6 08:19:25 xps kernel: [93020.924360] gsd-housekeepin D0 1729 1350 0 Creating a task against gnome-settings-daemon in case a workaround is possible. ** Also affects: gnome-settings-daemon (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/1702368 Title: Mounted sshfs filesystems sometimes prevent suspend Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in sshfs-fuse package in Ubuntu: New Bug description: Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a file on an sshfs filesystem. Sometimes when I suspend I get: Jul 4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done. Jul 4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep (mem) Jul 4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... Jul 4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): Jul 4 20:59:08 xps kernel: [46704.620534] gvimD0 11155 1336 0x0004 Jul 4 20:59:08 xps kernel: [46704.620541] Call Trace: Jul 4 20:59:08 xps kernel: [46704.620556] __schedule+0x233/0x6f0 ... Jul 4 20:59:08 xps kernel: [46704.620679] entry_SYSCALL_64_fastpath+0x1e/0xad ... Jul 4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done. ...and the system fails to suspend. AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an extensive explanation. The corresponding Debian bug was closed long ago due to inactivity. It isn't exactly bug 388419 though since that is about behaviour after resume, rather than failure to suspend. This affects sshfs-fuse, but it sounds like a full fix would be in the kernel. I wonder if it's possible to work around in userspace packaging in sshfs-fuse, though, by arranging some action in userspace before suspend? It seems unlikely that this will be addressed any time soon, but it'd be nice to keep a bug open in Launchpad so that users can have a single rallying point. --- ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 1519 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: sshfs-fuse ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 Tags: artful Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701085] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Many 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/1701085 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: The updated started and kept running for more than 30 minutes without any activity at all. It just halted. When I reboot the computer I got the error message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1601 F pulseaudio Date: Wed Jun 28 17:45:42 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=b15ac561-1f43-439b-acd7-864235fec616 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=56a7e809-b250-4de5-b5be-a9dd24718f75 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/01/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.05 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.05:bd03/01/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493839] Re: overlayfs: disabling V1 support leads to compile failure
fs: overlay: fix compile error when CONFIG_OVERLAY_FS_V1 is not set Fixes Ubuntu Launchpad Bug #1493839 Added necessary #ifdef around undeclared ovl_v1_fs_type according to CodingStyle lines 910-915 Signed-off-by: Achim Schreiber** Attachment added: "patch_launchpad_bug_1493839" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+attachment/4910248/+files/patch_launchpad_bug_1493839 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1493839 Title: overlayfs: disabling V1 support leads to compile failure Status in linux package in Ubuntu: Triaged Bug description: "CONFIG_OVERLAY_FS_V1 is not set": fs/overlayfs/super.c: In function 'ovl_init': fs/overlayfs/super.c:1213:30: error: 'ovl_v1_fs_type' undeclared (first use in this function) fs/overlayfs/super.c:1213:30: note: each undeclared identifier is reported only once for each function it appears in fs/overlayfs/super.c: In function 'ovl_exit': fs/overlayfs/super.c:1226:26: error: 'ovl_v1_fs_type' undeclared (first use in this function) scripts/Makefile.build:258: recipe for target 'fs/overlayfs/super.o' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702665] [NEW] 4.4.0-83-generic + Docker + EC2 t2.small frequently crashes at cgroup_rmdir GPF
Public bug reported: We run xenial-based Docker container hosts on EC2 with Amazon ECS. Recently we refreshed our base image, we started to see frequent panic. Hosts run Amazon ECS Agent, and the agent automatically creates or destroys Docker container based on requests onto ECS cluster. I think this crash is caused by Docker-related operations, because crashing at cgroups. Also, we're running several different cluster with another EC2 instance types, using same image. This problem is only reproducing at t2.small instances. (We also run c4.large and m4.* clusters) Our previous image ran 4.4.0-79-generic, and we see no problem with 79. [30558.783899] general protection fault: [#1] SMP [30558.784056] Modules linked in: veth binfmt_misc xt_nat xt_comment xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc isofs ppdev input_leds serio_raw parport_pc parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy [30558.784056] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-83-generic #106-Ubuntu [30558.784056] Hardware name: Xen HVM domU, BIOS 4.2.amazon 02/16/2017 [30558.784056] task: 88007c4e8000 ti: 88007c4e4000 task.ti: 88007c4e4000 [30558.784056] RIP: 0010:[] [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP: 0018:88007c4e7e40 EFLAGS: 00010212 [30558.784056] RAX: 8800114481bd RBX: 88002827ba50 RCX: 88007ab8d150 [30558.784056] RDX: 00111e7e0088 RSI: 88002827ba54 RDI: 8217745c [30558.784056] RBP: 88007c4e7e60 R08: 0020 R09: 88007c4e7e70 [30558.784056] R10: 0637760b R11: 880011829a80 R12: 88007ab8d000 [30558.784056] R13: R14: 559b48b2dcc0 R15: ff9c [30558.784056] FS: 7f29cf0db8c0() GS:88007d20() knlGS: [30558.784056] CS: 0010 DS: ES: CR0: 80050033 [30558.784056] CR2: 7fa466d58180 CR3: 7c19 CR4: 001406f0 [30558.784056] Stack: [30558.784056] 88002827ba50 88002827ba50 8800373e70d0 559b48b2dcc0 [30558.784056] 88007c4e7e80 811194b3 88002827ba50 [30558.784056] 88007c4e7ea0 8128ddcd 880011829a80 [30558.784056] Call Trace: [30558.784056] [] cgroup_rmdir+0x23/0x40 [30558.784056] [] kernfs_iop_rmdir+0x4d/0x80 [30558.784056] [] vfs_rmdir+0xb4/0x130 [30558.784056] [] do_rmdir+0x1df/0x200 [30558.784056] [] SyS_rmdir+0x16/0x20 [30558.784056] [] entry_SYSCALL_64_fastpath+0x16/0x71 [30558.784056] Code: 74 fd 48 c7 c7 5c 74 17 82 e8 8e 72 72 00 49 8b 94 24 50 01 00 00 49 8d 8c 24 50 01 00 00 48 39 d1 48 8d 42 f0 74 18 48 8b 50 08 82 b0 01 00 00 01 48 8b 50 10 48 39 d1 48 8d 42 f0 75 e8 49 [30558.784056] RIP [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP [30558.960828] ---[ end trace 7634e03ff94e8934 ]--- [30558.964811] Kernel panic - not syncing: Fatal exception in interrupt [30558.968805] Kernel Offset: disabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 6 10:22 seq crw-rw 1 root audio 116, 33 Jul 6 10:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.6 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: Thu Jul 6 10:27:37 2017 Ec2AMI: ami-34100353 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: t2.small 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: SHELL=/bin/bash TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=f76be987-234f-4071-87d4-06318cfc2135 ro cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/16/2017 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias:
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Hello FZ (sirfz), thank you very much for this info. Can you please tell me what is your Nvidia driver? I installed Ubuntu 17.04 while it was still in development, here is my xinput list (Kernel 4.11.8; Nvidia 381.22) $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouseid=12 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=14 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=15 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpadid=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=10 [slave keyboard (3)] ↳ G-SPY USB Gaming Mouseid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=13 [slave keyboard (3)] ↳ Asus WMI hotkeys id=17 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=18 [slave keyboard (3)] ↳ G-SPY USB Gaming Mouseid=19 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKeyid=20 [slave keyboard (3)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
acelankao, In 1692836 the same hack mentioned by Kalle was applied. I am not sure it is a proper fix though as it has not landed upstream: http://elixir.free- electrons.com/linux/latest/source/drivers/net/wireless/ath/ath10k/mac.c#L4181 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update (2017-05-20): Kalle Valo suggested a hack which increased client -> AP TCP performance - so it does not look like a firmware issue as I thought originally, rather an ath10k driver issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11 https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom) Tested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17 Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ - 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0:
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I can repeatably get this problem if I boot without a network connection.I get the message "waiting for a start job to complete ... Raise Network Interfaces" followed by "NMI Watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0]" Booting with a network cable attached has no problems. This is on 4.10.0-26 and AMD Athlon 64 X2, using an AMD GPU. Nouveau module is not loaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ?
[Kernel-packages] [Bug 1693393] Re: Power consumption issue on suspend-to-idle(s2idle)
** Changed in: hwe-next Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693393 Title: Power consumption issue on suspend-to-idle(s2idle) Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: The power consumption is pretty high(8Watt) during suspend-to-idle mode under Xenial. 1. It consumes 8Watt under 4.4 kernel 2. It consumes 4Watt under 4.8 kernel 3. It consumes 2Watt under 4.11 kernel There are essential patches in 4.8 and 4.11 kernels, they are In 4.8 9d26d3a PCI: Put PCIe ports into D3 during suspend In 4.11 8d2c453 platform/x86: dell-laptop: Add Latitude 7480 and others to the DMI whitelist We need these 2 commits to have better s2idle support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1693393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
I installed the latest stable Nvidia driver from the graphics-drivers repo. Driver Version: 375.66. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P:
[Kernel-packages] [Bug 1702665] 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/1702665 Title: 4.4.0-83-generic + Docker + EC2 t2.small frequently crashes at cgroup_rmdir GPF Status in linux package in Ubuntu: Confirmed Bug description: We run xenial-based Docker container hosts on EC2 with Amazon ECS. Recently we refreshed our base image, we started to see frequent panic. Hosts run Amazon ECS Agent, and the agent automatically creates or destroys Docker container based on requests onto ECS cluster. I think this crash is caused by Docker-related operations, because crashing at cgroups. Also, we're running several different cluster with another EC2 instance types, using same image. This problem is only reproducing at t2.small instances. (We also run c4.large and m4.* clusters) Our previous image ran 4.4.0-79-generic, and we see no problem with 79. [30558.783899] general protection fault: [#1] SMP [30558.784056] Modules linked in: veth binfmt_misc xt_nat xt_comment xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc isofs ppdev input_leds serio_raw parport_pc parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy [30558.784056] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-83-generic #106-Ubuntu [30558.784056] Hardware name: Xen HVM domU, BIOS 4.2.amazon 02/16/2017 [30558.784056] task: 88007c4e8000 ti: 88007c4e4000 task.ti: 88007c4e4000 [30558.784056] RIP: 0010:[] [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP: 0018:88007c4e7e40 EFLAGS: 00010212 [30558.784056] RAX: 8800114481bd RBX: 88002827ba50 RCX: 88007ab8d150 [30558.784056] RDX: 00111e7e0088 RSI: 88002827ba54 RDI: 8217745c [30558.784056] RBP: 88007c4e7e60 R08: 0020 R09: 88007c4e7e70 [30558.784056] R10: 0637760b R11: 880011829a80 R12: 88007ab8d000 [30558.784056] R13: R14: 559b48b2dcc0 R15: ff9c [30558.784056] FS: 7f29cf0db8c0() GS:88007d20() knlGS: [30558.784056] CS: 0010 DS: ES: CR0: 80050033 [30558.784056] CR2: 7fa466d58180 CR3: 7c19 CR4: 001406f0 [30558.784056] Stack: [30558.784056] 88002827ba50 88002827ba50 8800373e70d0 559b48b2dcc0 [30558.784056] 88007c4e7e80 811194b3 88002827ba50 [30558.784056] 88007c4e7ea0 8128ddcd 880011829a80 [30558.784056] Call Trace: [30558.784056] [] cgroup_rmdir+0x23/0x40 [30558.784056] [] kernfs_iop_rmdir+0x4d/0x80 [30558.784056] [] vfs_rmdir+0xb4/0x130 [30558.784056] [] do_rmdir+0x1df/0x200 [30558.784056] [] SyS_rmdir+0x16/0x20 [30558.784056] [] entry_SYSCALL_64_fastpath+0x16/0x71 [30558.784056] Code: 74 fd 48 c7 c7 5c 74 17 82 e8 8e 72 72 00 49 8b 94 24 50 01 00 00 49 8d 8c 24 50 01 00 00 48 39 d1 48 8d 42 f0 74 18 48 8b 50 08 82 b0 01 00 00 01 48 8b 50 10 48 39 d1 48 8d 42 f0 75 e8 49 [30558.784056] RIP [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP [30558.960828] ---[ end trace 7634e03ff94e8934 ]--- [30558.964811] Kernel panic - not syncing: Fatal exception in interrupt [30558.968805] Kernel Offset: disabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 6 10:22 seq crw-rw 1 root audio 116, 33 Jul 6 10:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.6 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: Thu Jul 6 10:27:37 2017 Ec2AMI: ami-34100353 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: t2.small 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: SHELL=/bin/bash TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=f76be987-234f-4071-87d4-06318cfc2135 ro
[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
I took the v4.12 kernel and compiled the LIS daemons from those sources as well. Reloading the Data Exchange service, KVP will fail with the below message. This is the same as initially reported, so nothing changed in the behavior. Not sure on the regression part, only up to the point on differences between distributions. KVP failure with v4.12 and Jul 6 01:18:55 xenial KVP: read failed; error:9 Bad file descriptor Jul 6 01:18:55 xenial systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Jul 6 01:18:55 xenial systemd[1]: hv-kvp-daemon.service: Unit entered failed state. Jul 6 01:18:55 xenial systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. After this error when systemd tries to start KVP again, if I manually do #systemctl start hv-kvp-daemon.service then the daemon will start just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701271] Re: linux: 4.11.0-10.15 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701271 Title: linux: 4.11.0-10.15 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released 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 Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-10.15 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 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/1701271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
I'm finding it hard to figure out why this failed. Can you upload the contents of the apt history logs to the bug report? You will find them in /var/log/apt/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1698363 Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Incomplete Bug description: Performing system updates, not a user of zfs (at this point). Packages just failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64) Fri Jun 16 07:19:28 CDT 2017 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.4.0-79-generic Date: Fri Jun 16 07:19:32 2017 InstallationDate: Installed on 2014-10-19 (971 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageVersion: 0.6.5.6-0ubuntu17 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1698363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700950] Re: Internal display not disabled for a docked Toshiba Portege Z30-A with closed lid and external monitor attached
Confirmed, fixed upstream. whoami@locahost:~$ uname -a Linux eclipse 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux whoami@locahost:~$ cat /etc/issue Ubuntu 17.04 \n \l ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700950 Title: Internal display not disabled for a docked Toshiba Portege Z30-A with closed lid and external monitor attached Status in linux package in Ubuntu: Confirmed Bug description: A grey background appears on the external monitor attached to the docking station of a (docked) Toshiba Portege Z30-A after booting up the system even when the lid is closed. After opening the lid it turns out that the login manager is actually shown on the internal display which should have been turned off altogether. This bug is similar to this one in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1430259 More info was also found here: https://bugzilla.redhat.com/show_bug.cgi?id=1447402 As per https://bugzilla.redhat.com/show_bug.cgi?id=1430259#c3 it seems that commit 77e9a4aa9de10cc1418bf9a892366988802a8025 may be the culprit as of kernel 4.10.10. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-generic 4.10.0.24.26 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: fortierv 4262 F pulseaudio /dev/snd/controlC2: fortierv 4262 F pulseaudio /dev/snd/controlC1: fortierv 4262 F pulseaudio /dev/snd/controlC0: fortierv 4262 F pulseaudio CurrentDesktop: XFCE Date: Wed Jun 28 05:56:01 2017 HibernationDevice: RESUME=UUID=5dac600d-b269-4c43-8afe-29a64fc9c65a InstallationDate: Installed on 2015-04-16 (804 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA PORTEGE Z30-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=7a8b097c-cbe0-4fff-bb5f-633f0e625cef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-01-28 (150 days ago) dmi.bios.date: 09/02/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 4.20 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z30-A dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion4.20:bd09/02/2015:svnTOSHIBA:pnPORTEGEZ30-A:pvrPT241C-02L002:rvnTOSHIBA:rnPORTEGEZ30-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z30-A dmi.product.version: PT241C-02L002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683340] Re: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build [make: *** No targets specified and no makefile found. Stop.]
I'm finding it hard to figure out why this failed. Can you upload the apt history logs to the bug report? You will find them in /var/log/apt/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1683340 Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build [make: *** No targets specified and no makefile found. Stop.] Status in zfs-linux package in Ubuntu: Confirmed Bug description: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 17.04 Package: zfs-dkms 0.6.5.9-5ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64) luni 17 aprilie 2017, 14:43:07 +0300 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.10.0-19-generic Date: Mon Apr 17 14:43:08 2017 InstallationDate: Installed on 2016-10-19 (180 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all PackageVersion: 0.6.5.9-5ubuntu4 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1683340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
** Changed in: zfs-linux (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1698363 Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Incomplete Bug description: Performing system updates, not a user of zfs (at this point). Packages just failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64) Fri Jun 16 07:19:28 CDT 2017 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.4.0-79-generic Date: Fri Jun 16 07:19:32 2017 InstallationDate: Installed on 2014-10-19 (971 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) PackageVersion: 0.6.5.6-0ubuntu17 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1698363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628553] Re: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop
Hi, if this is still and issue please let me know. I'm going to close the bug if I don't get any response in 1 week. ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1628553 Title: Ubuntu 16.04.1 Install zfsutils-linux Panic Error, endless loop Status in Native ZFS for Linux: Unknown Status in zfs-linux package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 16.04.1, installed all updates / upgrades for system before installing zfsutils-linux. The install processes all the way to Reached target Swap then has a PANIC error and loops endlessly. There is a zpool there already (was) with 3TB of data on it. This only happened after the system upgrade, so I reinstalled the boot drive / OS to see if it was just a issue with that, clearly it's an issue with the zfsutils-linux package for 16.04.1 Package version installed zfsutils-linux 0.6.5.6-0ubuntu12 Screenshot attached as I can't actually do anything once the boot gets to this stage: To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1628553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493839] Re: overlayfs: disabling V1 support leads to compile failure
** 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/1493839 Title: overlayfs: disabling V1 support leads to compile failure Status in linux package in Ubuntu: Triaged Bug description: "CONFIG_OVERLAY_FS_V1 is not set": fs/overlayfs/super.c: In function 'ovl_init': fs/overlayfs/super.c:1213:30: error: 'ovl_v1_fs_type' undeclared (first use in this function) fs/overlayfs/super.c:1213:30: note: each undeclared identifier is reported only once for each function it appears in fs/overlayfs/super.c: In function 'ovl_exit': fs/overlayfs/super.c:1226:26: error: 'ovl_v1_fs_type' undeclared (first use in this function) scripts/Makefile.build:258: recipe for target 'fs/overlayfs/super.o' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701744] Re: [Hyper-V] Add infiniband support for Azure HPC
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu) Status: New => Triaged ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701744 Title: [Hyper-V] Add infiniband support for Azure HPC Status in linux-azure package in Ubuntu: Triaged Bug description: This is the infiniband driver for Azure HPC. Windows Azure agent will provision an image for running infiniband RDMA via DAPL when "OS.EnableRDMA=y" is defined in waagent.conf. Note: Ubuntu image needs to load rdma_ucm on boot to expose the RDMA CM interface to user-mode library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1701744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701744] Re: [Hyper-V] Add infiniband support for Azure HPC
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701744 Title: [Hyper-V] Add infiniband support for Azure HPC Status in linux-azure package in Ubuntu: Triaged Bug description: This is the infiniband driver for Azure HPC. Windows Azure agent will provision an image for running infiniband RDMA via DAPL when "OS.EnableRDMA=y" is defined in waagent.conf. Note: Ubuntu image needs to load rdma_ucm on boot to expose the RDMA CM interface to user-mode library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1701744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Same here, bios version G752VS.306. I also replaced Windows completely (no dual-boot). It's really strange since the touchpad was completely dead in both Live Ubuntu and after installing and upgrading Ubuntu. Yesterday I just installed Chrome and later run a software update which updated 2 or 3 packages and that's it. Later that night I used the touchpad out of habit after opening the lid and after a few seconds I remembered that it wasn't supposed to be working but here it is, fully functional. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
[Kernel-packages] [Bug 1702685] [NEW] No wifi connectivity with kernel 4.4.0-83
Public bug reported: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702685 Title: No wifi connectivity with kernel 4.4.0-83 Status in linux package in Ubuntu: New Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701334] Re: package linux-headers-4.4.0-83 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-83/drivers/usb/gadget/legacy/Kconfig.dpkg-new
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** 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/1701334 Title: package linux-headers-4.4.0-83 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.4.0-83/drivers/usb/gadget/legacy/Kconfig.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: I've been having problems with the computer freezing for awhile, especially immediately upon opening firefox. I don't know if this is connected. I've been unable to get the 83 kernel to install, I had to do the repair steps to force the dpkg, but i guess it didn't work cause now it says can't install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-83 (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stephen2278 F...m pulseaudio /dev/snd/controlC0: stephen2278 F pulseaudio Date: Thu Jun 29 22:10:41 2017 DuplicateSignature: package:linux-headers-4.4.0-83:(not installed) Unpacking linux-image-extra-4.4.0-83-generic (4.4.0-83.106) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-extra-4.4.0-83-generic_4.4.0-83.106_amd64.deb (--unpack): unable to open '/lib/modules/4.4.0-83-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.4.0-83/drivers/usb/gadget/legacy/Kconfig.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=d252be08-8d41-4839-a829-af0016222534 InstallationDate: Installed on 2016-09-27 (275 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X55CR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.4.0-83 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.4.0-83/drivers/usb/gadget/legacy/Kconfig.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55CR.404 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55CR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55CR.404:bd09/20/2012:svnASUSTeKCOMPUTERINC.:pnX55CR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55CR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X55CR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701296] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701296 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: the download stopped halfway ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: einar 1391 F pulseaudio Date: Thu Jun 29 15:28:00 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-20 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Compaq nw8440 (RH418EA#ABN) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=4cd49b75-99df-4f6f-9159-3cb3d9398139 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YVD Ver. F.0F dmi.board.name: 30A3 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.17 dmi.chassis.asset.tag: CNU7192PS1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YVDVer.F.0F:bd12/19/2006:svnHewlett-Packard:pnHPCompaqnw8440(RH418EA#ABN):pvrF.0F:rvnHewlett-Packard:rn30A3:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nw8440 (RH418EA#ABN) dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701423] Re: APST quirk needed for Samsung 256GB NVMe drive
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701423 Title: APST quirk needed for Samsung 256GB NVMe drive Status in linux package in Ubuntu: Incomplete Bug description: This bug is a follow on from a previously fixed bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 The nature of this bug is identical to the previously reported bug, however it also affects 256GB drives as well. The wording at the start is a bit confusing, as it states that the 256GB drive already has a quirk added. Following the trail back a little, however, shows that a fix for high power drain was introduced, which then caused the NVMe controller lockups and system hangs. I am running Ubuntu 16.04 with HWE kernel [4.8.x, yakkety] on a Dell XPS15 9550 with a Samsung 256GB NVMe SSD. This bug commenced with the kernel linux (4.8.0-47.50) yakkety, with the specific change found at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602 ** Here is my output of nvme-cli ** nvme list Node SN Model Version Namespace Usage Format FW Rev - -- /dev/nvme0n1 S29NNXAGC38399 PM951 NVMe SAMSUNG 256GB 1.1 1 201.30 GB / 256.06 GB 512 B + 0 B BXV77D0Q nvme id-ctrl /dev/nvme0n1 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S29NNXAGC38399 mn : PM951 NVMe SAMSUNG 256GB fr : BXV77D0Q rab : 2 ieee : 002538 cmic : 0 mdts : 5 cntlid : 1 ver : 0 rtd3r : 0 rtd3e : 0 oaes : 0 oacs : 0x17 acl : 7 aerl : 3 frmw : 0x6 lpa : 0 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 0 cctemp : 0 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 0 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- Also, as requested: lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1910] (rev 07) 00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) [8086:1901] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 07) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H LPSS I2C Controller #0 [8086:a160] (rev 31) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H LPSS I2C Controller #1 [8086:a161] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] [8086:a103] (rev 31) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #1 [8086:a110] (rev f1) 00:1c.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1) 00:1d.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #15 [8086:a11e] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a14e] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev a2) 02:00.0 Network controller [0280]: Broadcom
[Kernel-packages] [Bug 1701351] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701351 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: stalled) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mediaserv 1427 F pulseaudio /dev/snd/controlC1: mediaserv 1427 F pulseaudio Date: Thu Jun 29 15:45:08 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-26 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. UN62 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=7923527b-b57d-4169-8794-5a26fffbe4c9 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2016 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed from AMI) dmi.bios.version: 1307 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: UN62 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedfromAMI):bvr1307:bd10/18/2016:svnASUSTeKCOMPUTERINC.:pnUN62:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnUN62:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: UN62 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver
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.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-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/1701316 Title: Data corruption with hio driver Status in linux package in Ubuntu: Confirmed Bug description: We are seeing data corruption issues using the hio driver with kernel 4.10.0 # uname -a Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Making xfs fails: root@arbok:~# mkfs.xfs /dev/hioa meta-data=/dev/hioa isize=512agcount=4, agsize=48835584 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=195342336, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=95382, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 bad magic number bad magic number Metadata corruption detected at xfs_sb block 0x0/0x200 libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200 The drive appears to be healthy. Firmware has been upgraded to ver 656: root@arbok:~# hio_info -d /dev/hioa hioaSerial number: 022XWV10G2000325 Size(GB): 800 Max size(GB): 800 Hardware version: 1.0 Firmware version: 656 Driver version: 2.1.0.28 Work mode: MLC Run time (sec.):8910490 Total read(MB):8499 Total write(MB):0 Lifetime remaining: 99.844% Max bad block rate: 0.167% Health: OK Comment:NA No relevant entries about read/write errors in dmesg Also just copying 8G random data and reading those back gives a hash mismatch: root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock sha256sum test.dat read- 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s root@arbok:~# sha256sum test.dat read-back.dat 6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702323] Re: update-initramfs hangs
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702323 Title: update-initramfs hangs Status in linux package in Ubuntu: Incomplete Bug description: I have a server running version 16.04.1 LTS and kernel 4.4.0-62-generic I ran apt-get upgrade and the upgrade process hangs on... update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic In a separate shell I have tried update-initramfs -u -v and the process stops on "Calling hook cryptroot" In my /boot/ directory I now have a file initrd.img-4.4.0-83-generic.new which is 0Kb in size. I do not have any encrypted volumes. Please can you suggest how I can get round this error and complete the upgrade. Many thanks Max To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702368 Title: Mounted sshfs filesystems sometimes prevent suspend Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in sshfs-fuse package in Ubuntu: New Bug description: Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30 and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against a file on an sshfs filesystem. Sometimes when I suspend I get: Jul 4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done. Jul 4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep (mem) Jul 4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... Jul 4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): Jul 4 20:59:08 xps kernel: [46704.620534] gvimD0 11155 1336 0x0004 Jul 4 20:59:08 xps kernel: [46704.620541] Call Trace: Jul 4 20:59:08 xps kernel: [46704.620556] __schedule+0x233/0x6f0 ... Jul 4 20:59:08 xps kernel: [46704.620679] entry_SYSCALL_64_fastpath+0x1e/0xad ... Jul 4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done. ...and the system fails to suspend. AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an extensive explanation. The corresponding Debian bug was closed long ago due to inactivity. It isn't exactly bug 388419 though since that is about behaviour after resume, rather than failure to suspend. This affects sshfs-fuse, but it sounds like a full fix would be in the kernel. I wonder if it's possible to work around in userspace packaging in sshfs-fuse, though, by arranging some action in userspace before suspend? It seems unlikely that this will be addressed any time soon, but it'd be nice to keep a bug open in Launchpad so that users can have a single rallying point. --- ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 1519 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: sshfs-fuse ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 Tags: artful Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701539] Re: dont know what to do
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701539 Title: dont know what to do Status in linux package in Ubuntu: Invalid Bug description: i am a Newb in Ubuntu .. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-81-generic 4.4.0-81.104 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: a 1896 F...m pulseaudio /dev/snd/controlC0: a 1896 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 30 13:52:01 2017 HibernationDevice: RESUME=UUID=8c8782a5-69a2-4e4e-83ce-dad1acd0f6b1 InstallationDate: Installed on 2017-05-17 (43 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Micro-Star International MSI NOTEBOOK VR630 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-81-generic N/A linux-backports-modules-4.4.0-81-generic N/A linux-firmware1.157.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1672NMS V1.0J dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-1672 dmi.board.vendor: MSI dmi.board.version: Ver 1.000 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1672NMSV1.0J:bd04/10/2009:svnMicro-StarInternational:pnMSINOTEBOOKVR630:pvrVer1.000:rvnMSI:rnMS-1672:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MSI NOTEBOOK VR630 dmi.product.version: Ver 1.000 dmi.sys.vendor: Micro-Star International To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1701499 Title: System often freezes or panics if I log in with Dell Dock WD15 connected Status in linux package in Ubuntu: Incomplete Bug description: I'm using Dell Precision 5520 with Ubuntu 17.04. If I first start a Unity session and then connect Dell WD15 USB-C dock with an external diplay plugged in, the system detects it properly and all the things work flawlessly (ethernet, external keyboard, external display, external storage connected to USB on the dock). I can plug-in and plug-out the dock multiple times and it just works. However if I boot the laptop with the dock already plugged in, first I get to the login screen and initially all is ok. Both screens are activated, and I can log in using the keyboard connected to the dock. When I hit "Enter", both screens go blank for a while, then they turn back on and I can see the desktop. A second or maybe two seconds later things start falling apart. When I move the mouse pointer a second after logging, it is kinda "jumpy", the movement is not smooth. The move freezes for a few times. I observed this behaviour only when moving the wireless mouse connected to the USB of the laptop. The builtin touchpad works smoothly. If it was the only issue, this would be a very minor annoyance. Sometimes, after a few short mouse pointer freezes the system starts working smoothly and all is rock stable from that point. However quite often I noticed much worse things happen: 1. The mouse pointer and everything freezes totally after a few seconds from displaying the desktop. It is not possible to switch to the console with Ctrl-Alt-F1. This happens in >50% of logins. 2. Kernel panic. I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more stable than 4.10.0-x) and also 4.12.rc5 which I tried once. Even if everything goes fine, I noticed the following errors printed in syslog. I'm not sure if they are related, but they look very iffy to me: Jun 30 10:46:23 p5520 kernel: [ 38.391971] DMAR: DRHD: handling fault status reg 2 Jun 30 10:46:23 p5520 kernel: [ 38.391977] DMAR: [INTR-REMAP] Request device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request due to source-id verification failure Jun 30 10:46:23 p5520 kernel: [ 38.472490] xhci_hcd :0a:00.0: remove, state 1 Jun 30 10:46:23 p5520 kernel: [ 38.472496] usb usb4: USB disconnect, device number 1 Jun 30 10:46:23 p5520 kernel: [ 38.472497] usb 4-1: USB disconnect, device number 2 Jun 30 10:46:23 p5520 kernel: [ 38.472498] usb 4-1.2: USB disconnect, device number 3 Jun 30 10:46:23 p5520 NetworkManager[1129]: [1498812383.7510] device (eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36] Jun 30 10:46:23 p5520 ModemManager[1076]: (net/eth0): released by modem /sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2 Jun 30 10:46:23 p5520 NetworkManager[1129]: [1498812383.7537] devices removed (path: /sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0, iface: eth0) Jun 30 10:46:23 p5520 kernel: [ 38.552718] xhci_hcd :0a:00.0: Host halt failed, -19 Jun 30 10:46:23 p5520 kernel: [ 38.552721] xhci_hcd :0a:00.0: Host not accessible, reset failed. Jun 30 10:46:23 p5520 kernel: [ 38.552722] xhci_hcd :0a:00.0: USB bus 4 deregistered Jun 30 10:46:23 p5520 kernel: [ 38.552728] xhci_hcd :0a:00.0: remove, state 1 Jun 30 10:46:23 p5520 kernel: [ 38.552731] usb usb3: USB disconnect, device number 1 Jun 30 10:46:23 p5520 kernel: [ 38.552732] usb 3-1: USB disconnect, device number 2 Jun 30 10:46:23 p5520 kernel: [ 38.552732] usb 3-1.5: USB disconnect, device number 3 Jun 30 10:46:23 p5520 kernel: [ 38.553322] usb 3-1.7: USB disconnect, device number 4 Jun 30 10:46:23 p5520 kernel: [ 38.556064] BUG: unable to handle kernel paging request at 002018387ad8 Jun 30 10:46:23 p5520 kernel: [ 38.556173] IP: __radix_tree_lookup+0x10/0xf0 Jun 30
[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701486 Title: System brightness slider doesn't work any more Status in linux package in Ubuntu: Incomplete Bug description: Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64 Cinnamon. Changing /sys/class/backlight/intel_backlight/brightness manually works though. $ cat /proc/version_signature Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM Registers [8086:1910] (rev 07) Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) [8086:1901] (rev 07) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller (x16) [8086:2015] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00218 Data: Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled+ CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
[Kernel-packages] [Bug 1701492] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701492 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: i was updating os through ubuntu software app. then it got stuck. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: samar 2316 F pulseaudio Date: Fri Jun 30 14:28:47 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-28 (32 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=f04bb9d0-4648-4171-b5b1-cdcc02754f04 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.216:bd11/20/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL552VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701471] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701471 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Problems since updating the latest Ubuntu version 17.? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nanka 1637 F pulseaudio Date: Fri Jun 30 03:02:00 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=a7ada202-7785-4942-8a15-f24aeb776fee InstallationDate: Installed on 2016-04-26 (429 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Compaq 6710b (KE124ET#ABH) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=a7e09155-e757-4c87-97a0-a84d52a8716a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-07 (23 days ago) dmi.bios.date: 04/10/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DDU Ver. F.11 dmi.board.name: 30C0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.2E dmi.chassis.asset.tag: CNU8191FQ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.11:bd04/10/2008:svnHewlett-Packard:pnHPCompaq6710b(KE124ET#ABH):pvrF.11:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6710b (KE124ET#ABH) dmi.product.version: F.11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701521] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701521 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Still remain ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olv1455 F pulseaudio Date: Fri Jun 30 12:24:56 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=0338ba34-0197-4d2b-b7cc-3ee1aec2497e InstallationDate: Installed on 2017-03-01 (120 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP Pavilion dv6700 Notebook PC ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=edbede00-adbd-455f-94d3-662c5b4dd9fc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-04-19 (71 days ago) dmi.bios.date: 05/21/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.57 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.57:bd05/21/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] 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/1702685 Title: No wifi connectivity with kernel 4.4.0-83 Status in linux package in Ubuntu: Confirmed Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs
When using the following kernel (the default Xenial kernel, aka ga-16.04 in MAAS), we see this issue: 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux When using the HWE kernel (aka hwe-16.04 in MAAS), we do NOT see this issue: 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702427] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1702427 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juan 1725 F pulseaudio Date: Tue Jul 4 17:54:44 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=d06c77a7-3851-4955-a421-8f1f2dbf29e9 InstallationDate: Installed on 2017-06-22 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 647358G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=bb5d6d55-46ab-4870-ab89-808959e01758 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7VET81WW (3.11 ) dmi.board.name: 647358G 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:bvr7VET81WW(3.11):bd11/19/2009:svnLENOVO:pn647358G:pvrThinkPadT400:rvnLENOVO:rn647358G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 647358G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701271] Re: linux: 4.11.0-10.15 -proposed tracker
** Changed in: kernel-development-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/promote-to-release 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/1701271 Title: linux: 4.11.0-10.15 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Fix Released 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: Confirmed Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-10.15 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 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/1701271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670137] Re: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc
Hi mahmoh, Out of interest, where did you get the info: cache nvme0n1p5 OFFLINE 0 0 0 sda3 ONLINE 0 0 0 ** Changed in: zfs-linux (Ubuntu) Status: New => In Progress ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1670137 Title: cache on NVMe inhibits proper suspend/hibernate - zfs l2arc Status in zfs-linux package in Ubuntu: In Progress Bug description: Please see: 2017-03-05 09:03 2017-03-05 14:03 UTCKernelOops linux-image-4.4.0-31-generic https://errors.ubuntu.com/oops/7bb2122e-01b1-11e7-ba2a-fa163e839e11 Running zfs [root] with l2arc cache enabled fails to suspend properly, screen goes blank but power stays on, when I disable the cache it works fine. Unsure if this happens with non-root install of zfs, slog does not cause this problem. Linux mp 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ii zfs-initramfs 0.6.5.6-0ubuntu15 all Native OpenZFS root filesystem capabilities for Linux ii zfs-zed0.6.5.6-0ubuntu15 amd64OpenZFS Event Daemon (zed) ii zfsutils-linux 0.6.5.6-0ubuntu15 amd64Native OpenZFS management utilities for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1670137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
My Ubuntu is fully updated, but my ELAN touchpad doesn't work. Next week I will perform a new clean installation, without Windows. Just one more thing: what is your BIOS version (my is latest available G752VS_BIOS.306)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [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)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
Are there any recommendations how to proceed with the EOL for yakkety set? I use zfs clones as inpromptu boot environments when updating and use ZFS datasets for docker and lxd, so I have a fair amount of 'canmount=none's and 'mountpoint=legacy's. I am reluctant to just c the script from yakkety over to zesty, but seriously short of better ideas. Cheers! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: Confirmed Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701994] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701994 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: I have ubuntu 17.04 ,but many time my laptop hanged. and many applications atomaticaly off. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mahipal1932 F pulseaudio Date: Mon Jul 3 01:23:04 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-23 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Inspiron 3521 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=6fa1b222-ab75-434c-b4bb-83c481628432 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0H579X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0H579X:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701931] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701931 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: update bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfb1868 F pulseaudio /dev/snd/controlC1: jfb1868 F pulseaudio Date: Thu Jun 29 23:24:24 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=7a0c6609-56a2-491a-a8da-13d4edfe1f2a InstallationDate: Installed on 2015-12-20 (560 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: TOSHIBA Satellite P200 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=db86c4ab-9a4a-478c-b1e5-7ddb61af6eb0 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-06-05 (391 days ago) dmi.bios.date: 09/27/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd09/27/2007:svnTOSHIBA:pnSatelliteP200:pvrPSPB6E-10S01XFR:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite P200 dmi.product.version: PSPB6E-10S01XFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701941] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701941 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Trying to update packages from software manager. I was able to complete the process using the command line. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1528 F pulseaudio developer 2132 F pulseaudio Date: Sun Jul 2 13:00:29 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=e52b783e-9827-420e-8a61-1234e25a4880 InstallationDate: Installed on 2017-04-28 (64 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2441AY9 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=2ee77639-b568-4471-b775-786be325f2b1 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET61WW (2.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 2441AY9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET61WW(2.03):bd09/13/2012:svnLENOVO:pn2441AY9:pvrThinkPadW530:rvnLENOVO:rn2441AY9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2441AY9 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701997] Re: package linux-image-extra-4.4.0-66-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-66-generic is not ready for configuration cann
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701997 Title: package linux-image-extra-4.4.0-66-generic (not installed) failed to install/upgrade: package linux-image-extra-4.4.0-66-generic is not ready for configuration cannot configure (current status 'half- installed') Status in linux package in Ubuntu: Incomplete Bug description: problem occured after cleaning up the boot directory which had run out of space for a couple of days ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-81-generic 4.4.0-81.104 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2484 F pulseaudio /dev/snd/controlC0: michael2484 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 3 06:14:34 2017 HibernationDevice: RESUME=UUID=7ea7b2bb-ca02-4936-bbe7-c5ee95855db2 InstallationDate: Installed on 2016-11-20 (224 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-81-generic N/A linux-backports-modules-4.4.0-81-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.0E dmi.board.name: 172B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.30 dmi.chassis.asset.tag: CZC04441YG dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0E:bd08/23/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.30:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701892] Re: [Artful] mlx5e-Introduce RX Page-Reuse
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Artful) Importance: Medium Status: Triaged ** 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/1701892 Title: [Artful] mlx5e-Introduce RX Page-Reuse Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: This feature is a Page-Reuse mechanism in non-Striding RQ RX datapath. A WQE (RX descriptor) buffer is a page, that in most cases was fully wasted on a packet that is much smaller, requiring a new page for the next round. In this feature, we implement a page-reuse mechanism, that resembles a `SW Striding RQ`. We allow the WQE to reuse its allocated page as much as it could, until the page is fully consumed. In each round, the WQE is capable of receiving packet of maximal size (MTU). Yet, upon the reception of a packet, the WQE knows the actual packet size, and consumes the exact amount of memory needed to build a linear SKB. Then, it updates the buffer pointer within the page accordingly, for the next round. Feature is mutually exclusive with XDP (packet-per-page) and LRO (session size is a power of two, needs unused page). Upstream acceptance Commits accd58833237 net/mlx5e: Introduce RX Page-Reuse bce2b2bf6682 net/mlx5e: Enhance RX SKB headroom logic 78aedd327982 net/mlx5e: Build SKB with exact frag_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk
** Changed in: makedumpfile (Ubuntu) Status: Triaged => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Zesty) Status: New => Invalid ** Changed in: makedumpfile (Ubuntu Trusty) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu Zesty) Assignee: (unassigned) => Louis Bouchard (louis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Trusty: Invalid Status in makedumpfile source package in Trusty: New Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Zesty: Invalid Status in makedumpfile source package in Zesty: New Bug description: Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0 [ 132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240 [ 132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110 [ 132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108 [ 132.643961] Instruction dump: [ 132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 3949ba60 [ 132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020
[Kernel-packages] [Bug 1416663] Re: package linux-firmware 1.127.10 failed to install/upgrade: el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1416663 Title: package linux-firmware 1.127.10 failed to install/upgrade: el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in linux-firmware package in Ubuntu: Confirmed Bug description: I was trying to reinstall gedit on terminal and suddenly an issue ocurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.10 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: linux-firmware: Configure Architecture: amd64 Date: Sat Jan 31 13:26:42 2015 Dependencies: DpkgTerminalLog: dpkg: error al procesar el paquete linux-firmware (--configure): el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-installed') DuplicateSignature: package:linux-firmware:1.127.10:el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-installed') ErrorMessage: el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2013-09-08 (510 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: linux-firmware Title: package linux-firmware 1.127.10 failed to install/upgrade: el paquete linux-firmware no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: Upgraded to trusty on 2014-10-05 (117 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1416663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702685 Title: No wifi connectivity with kernel 4.4.0-83 Status in linux package in Ubuntu: Incomplete Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702665] Re: 4.4.0-83-generic + Docker + EC2 t2.small frequently crashes at cgroup_rmdir GPF
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Also affects: docker (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/1702665 Title: 4.4.0-83-generic + Docker + EC2 t2.small frequently crashes at cgroup_rmdir GPF Status in docker package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: We run xenial-based Docker container hosts on EC2 with Amazon ECS. Recently we refreshed our base image, we started to see frequent panic. Hosts run Amazon ECS Agent, and the agent automatically creates or destroys Docker container based on requests onto ECS cluster. I think this crash is caused by Docker-related operations, because crashing at cgroups. Also, we're running several different cluster with another EC2 instance types, using same image. This problem is only reproducing at t2.small instances. (We also run c4.large and m4.* clusters) Our previous image ran 4.4.0-79-generic, and we see no problem with 79. [30558.783899] general protection fault: [#1] SMP [30558.784056] Modules linked in: veth binfmt_misc xt_nat xt_comment xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc isofs ppdev input_leds serio_raw parport_pc parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy [30558.784056] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-83-generic #106-Ubuntu [30558.784056] Hardware name: Xen HVM domU, BIOS 4.2.amazon 02/16/2017 [30558.784056] task: 88007c4e8000 ti: 88007c4e4000 task.ti: 88007c4e4000 [30558.784056] RIP: 0010:[] [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP: 0018:88007c4e7e40 EFLAGS: 00010212 [30558.784056] RAX: 8800114481bd RBX: 88002827ba50 RCX: 88007ab8d150 [30558.784056] RDX: 00111e7e0088 RSI: 88002827ba54 RDI: 8217745c [30558.784056] RBP: 88007c4e7e60 R08: 0020 R09: 88007c4e7e70 [30558.784056] R10: 0637760b R11: 880011829a80 R12: 88007ab8d000 [30558.784056] R13: R14: 559b48b2dcc0 R15: ff9c [30558.784056] FS: 7f29cf0db8c0() GS:88007d20() knlGS: [30558.784056] CS: 0010 DS: ES: CR0: 80050033 [30558.784056] CR2: 7fa466d58180 CR3: 7c19 CR4: 001406f0 [30558.784056] Stack: [30558.784056] 88002827ba50 88002827ba50 8800373e70d0 559b48b2dcc0 [30558.784056] 88007c4e7e80 811194b3 88002827ba50 [30558.784056] 88007c4e7ea0 8128ddcd 880011829a80 [30558.784056] Call Trace: [30558.784056] [] cgroup_rmdir+0x23/0x40 [30558.784056] [] kernfs_iop_rmdir+0x4d/0x80 [30558.784056] [] vfs_rmdir+0xb4/0x130 [30558.784056] [] do_rmdir+0x1df/0x200 [30558.784056] [] SyS_rmdir+0x16/0x20 [30558.784056] [] entry_SYSCALL_64_fastpath+0x16/0x71 [30558.784056] Code: 74 fd 48 c7 c7 5c 74 17 82 e8 8e 72 72 00 49 8b 94 24 50 01 00 00 49 8d 8c 24 50 01 00 00 48 39 d1 48 8d 42 f0 74 18 48 8b 50 08 82 b0 01 00 00 01 48 8b 50 10 48 39 d1 48 8d 42 f0 75 e8 49 [30558.784056] RIP [] cgroup_destroy_locked+0x5f/0xf0 [30558.784056] RSP [30558.960828] ---[ end trace 7634e03ff94e8934 ]--- [30558.964811] Kernel panic - not syncing: Fatal exception in interrupt [30558.968805] Kernel Offset: disabled ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 6 10:22 seq crw-rw 1 root audio 116, 33 Jul 6 10:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.6 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
[Kernel-packages] [Bug 1701778] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701778 Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: da error al actualizar ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andres 1864 F pulseaudio Date: Sat Jul 1 07:30:27 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-19 (11 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: System manufacturer P5K ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=dd470c89-aaa1-49b3-a79b-3eedcdd197b1 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1006 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K 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.:bvr1006:bd03/05/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K 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/1701778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701775] Re: [STAGING] package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701775 Title: [STAGING] package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: die Installation hing sich auch bzw. sie lief nicht weiter, der Fortschrittsbalken blieb bis zum ausschalten des Rechners an einer Stelle stehen. Vorher meldete das System ubuntu 17.04 mir über Ubuntu Software, es seien Betriebssystemakualisierungen zu installieren. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: roman 1880 F pulseaudio /dev/snd/controlC0: roman 1880 F pulseaudio Date: Fri Jun 30 19:38:43 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-27 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: MSI MS-7693 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=5e8e3d65-5247-48ca-9fb1-2be6a2921a20 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 RfKill: SourcePackage: linux StagingDrivers: r8712u Title: [STAGING] package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd12/26/2012:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7693 dmi.product.version: 3.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702427] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701085 *** https://bugs.launchpad.net/bugs/1701085 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1701085, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1701085 package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1702427 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 lts ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juan 1725 F pulseaudio Date: Tue Jul 4 17:54:44 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=d06c77a7-3851-4955-a421-8f1f2dbf29e9 InstallationDate: Installed on 2017-06-22 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 647358G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=bb5d6d55-46ab-4870-ab89-808959e01758 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7VET81WW (3.11 ) dmi.board.name: 647358G 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:bvr7VET81WW(3.11):bd11/19/2009:svnLENOVO:pn647358G:pvrThinkPadT400:rvnLENOVO:rn647358G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 647358G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701888] Re: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701888 Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: seems to be not installed ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: juan 1884 F pulseaudio /dev/snd/controlC0: juan 1884 F pulseaudio Date: Sat Jul 1 16:21:23 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=4c19c813-cc45-4267-ac3e-6309d6edae99 InstallationDate: Installed on 2017-01-14 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire 5560 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=61bb2b36-476f-4434-bd5c-f001031fd4bf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1 SourcePackage: linux Title: package linux-image-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-04-14 (78 days ago) dmi.bios.date: 12/05/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire 5560 dmi.board.vendor: Acer dmi.board.version: A11 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.15:bd12/05/2011:svnAcer:pnAspire5560:pvr0.1:rvnAcer:rnAspire5560:rvrA11:cvnAcer:ct9:cvr0.1: dmi.product.name: Aspire 5560 dmi.product.version: 0.1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701860] Re: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1701860 Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Incomplete Bug description: packages broken after normal update, apt-get install -f does not work other software will not install - says waiting to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: anita 2101 F...m pulseaudio /dev/snd/controlC0: anita 2101 F pulseaudio Date: Sat Jul 1 18:58:25 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=e6adb2ec-8b4e-4018-91b1-fd86e50db776 InstallationDate: Installed on 2014-06-11 (1116 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 6474E8U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=77261f15-83fc-4126-8aaf-19100070790d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11 SourcePackage: linux Title: package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-06-08 (23 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474E8U 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:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474E8U:pvrThinkPadT400:rvnLENOVO:rn6474E8U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474E8U dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1701857] Re: Kernel Oops - unable to handle kernel paging request; RIP: 0010:[] [] fput+0x5/0x90
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.12 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.12 ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701857 Title: Kernel Oops - unable to handle kernel paging request; RIP: 0010:[] [] fput+0x5/0x90 Status in linux package in Ubuntu: Confirmed Bug description: Kernel Oops causing system to become unresponsive (cannot SSH in or get a console on screen via CTRL-ALT-F1). Requires hard reset to bring system back up. Sorry I'm new to reporting these sort of bugs so unsure if I've supplied sufficient information! From kern.log: Jul 2 05:07:10 Ultimate kernel: [117260.361284] BUG: unable to handle kernel paging request at 4038 Jul 2 05:07:10 Ultimate kernel: [117260.361310] IP: [] fput+0x5/0x90 Jul 2 05:07:10 Ultimate kernel: [117260.361321] PGD 0 Jul 2 05:07:10 Ultimate kernel: [117260.361327] Oops: 0002 [#1] SMP Jul 2 05:07:10 Ultimate kernel: [117260.361334] Modules linked in: scsi_transport_iscsi nvram msr ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter aufs binfmt_misc veth pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) snd_usb_audio snd_usbmidi_lib bridge stp llc input_leds joydev iptable_filter ip_tables x_tables gspca_zc3xx gspca_main v4l2_common videodev media snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_intel snd_hda_codec snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event snd_pcm snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mei_me mei shpchp lpc_ich 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 hid_generic psmou se nouveau uas usb_storage mxm_wmi wmi firewire_ohci usbhid hid pata_acpi i2c_algo_bit firewire_core ttm crc_itu_t drm_kms_helper r8169 syscopyarea mii sysfillrect sysimgblt fb_sys_fops drm fjes video Jul 2 05:07:10 Ultimate kernel: [117260.361581] CPU: 1 PID: 29214 Comm: systemd-cgroups Tainted: GB OE 4.4.0-83-generic #106-Ubuntu Jul 2 05:07:10 Ultimate kernel: [117260.361591] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H61M-S2PV, BIOS FE 06/21/2012 Jul 2 05:07:10 Ultimate kernel: [117260.361600] task: 880269446800 ti: 88028f394000 task.ti: 88028f394000 Jul 2 05:07:10 Ultimate kernel: [117260.361608] RIP: 0010:[] [] fput+0x5/0x90 Jul 2 05:07:10 Ultimate kernel: [117260.361618] RSP: 0018:88028f397d90 EFLAGS: 00010206 Jul 2 05:07:10 Ultimate kernel: [117260.361624] RAX: RBX: 8801fefad000 RCX: 88029ed1a860 Jul 2 05:07:10 Ultimate kernel: [117260.361631] RDX: 0116 RSI: 81a28148 RDI: 4000 Jul 2 05:07:10 Ultimate kernel: [117260.361638] RBP: 88028f397da8 R08: 0002 R09: 0282 Jul 2 05:07:10 Ultimate kernel: [117260.361646] R10: R11: 000b R12: 4000 Jul 2 05:07:10 Ultimate kernel: [117260.361653] R13: 88028f383400 R14: R15: 88028f383468 Jul 2 05:07:10 Ultimate kernel: [117260.361661] FS: () GS:88029ed0() knlGS: Jul 2 05:07:10 Ultimate kernel: [117260.361669] CS: 0010 DS: ES: CR0: 80050033 Jul 2 05:07:10 Ultimate kernel: [117260.361675] CR2: 4038 CR3: 0fe0a000 CR4: 000406e0 Jul 2 05:07:10 Ultimate kernel: [117260.361682] Stack: Jul 2 05:07:10 Ultimate kernel: [117260.361686] 811bc514 88028fb3e3e8 88028fb3e578 88028f397dc8 Jul 2 05:07:10 Ultimate kernel: [117260.361698] 811c68e0 88028f383400 88028f397e78 Jul 2 05:07:10 Ultimate kernel: [117260.361711] 811ca1c9 88028fb3e3e8 88028f383400 Jul 2 05:07:10 Ultimate kernel: [117260.361723] Call Trace: Jul 2 05:07:10 Ultimate kernel: [117260.361732] [] ? vma_do_fput+0x34/0x40 Jul 2 05:07:10
[Kernel-packages] [Bug 1701873] Re: Unable to boot with Latest kernel 4.4.0-83 update
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable 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'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.4.76 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Tags added: needs-bisect ** Tags removed: kernel-da-key ** Tags added: kernel-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/1701873 Title: Unable to boot with Latest kernel 4.4.0-83 update Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Since the update (linux-image-4.4.0-83-generic), I can't boot Ubuntu anymore. First boot, freeze on desktop with clock freezed (seconds don't increment) Second boot, Freeze during boot process 3rd boot, freezed even earlier in the boot process. Each time I had to manually shutdown my computer by pressing the power button. If I choose the previous kernel version linux-image-4.4.0-81-generic, it works just fine. Note that I gathered option using ubuntu-bug linux, but obviously, it's with the previous linux kernel, the one that works. So everything should be accurate BUT the kernel version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-81-generic 4.4.0-81.104 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: autiwa 1582 F pulseaudio /dev/snd/controlC2: autiwa 1582 F pulseaudio /dev/snd/controlC0: autiwa 1582 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 2 09:03:43 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-18 (133 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic root=UUID=c70c100f-9849-4af7-b47e-41440bbba94d ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-81-generic N/A linux-backports-modules-4.4.0-81-generic N/A linux-firmware1.157.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1007 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-A 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.:bvr1007:bd05/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx: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/1701873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
skb_orphan() is not the way to go. Can someone try the following patch ? diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c index 4e985dea1dd24fdecfbf9b47d51cff698e97cd2f..5f394f2f524f6ac8d8d9bef50a1bfc99397d6724 100644 --- a/net/ipv4/tcp_output.c +++ b/net/ipv4/tcp_output.c @@ -2158,7 +2158,7 @@ static bool tcp_pacing_check(const struct sock *sk) } /* TCP Small Queues : - * Control number of packets in qdisc/devices to two packets / or ~1 ms. + * Control number of packets in qdisc/devices to two packets / or ~4 ms. * (These limits are doubled for retransmits) * This allows for : * - better RTT estimation and ACK scheduling @@ -2173,7 +2173,7 @@ static bool tcp_small_queue_check(struct sock *sk, const struct sk_buff *skb, { unsigned int limit; - limit = max(2 * skb->truesize, sk->sk_pacing_rate >> 10); + limit = max(2 * skb->truesize, sk->sk_pacing_rate >> 8); limit = min_t(u32, limit, sysctl_tcp_limit_output_bytes); limit <<= factor; -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update (2017-05-20): Kalle Valo suggested a hack which increased client -> AP TCP performance - so it does not look like a firmware issue as I thought originally, rather an ath10k driver issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11 https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom) Tested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17 Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ - 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0:
[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver
Indeed this issue started after upgrading to 4.10.0-26-generic. We've been using 4.8.0-34-generic previously, and didn't see that issue there. The hio driver is not present upstream, it's been included in xenial with Bug #1603483. Also, we've had consistency issues with this driver before (cf. Bug #1646643), but afaics the patches from that bug are included in 4.10.0-26-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701316 Title: Data corruption with hio driver Status in linux package in Ubuntu: Confirmed Bug description: We are seeing data corruption issues using the hio driver with kernel 4.10.0 # uname -a Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Making xfs fails: root@arbok:~# mkfs.xfs /dev/hioa meta-data=/dev/hioa isize=512agcount=4, agsize=48835584 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=195342336, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=95382, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 bad magic number bad magic number Metadata corruption detected at xfs_sb block 0x0/0x200 libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200 The drive appears to be healthy. Firmware has been upgraded to ver 656: root@arbok:~# hio_info -d /dev/hioa hioaSerial number: 022XWV10G2000325 Size(GB): 800 Max size(GB): 800 Hardware version: 1.0 Firmware version: 656 Driver version: 2.1.0.28 Work mode: MLC Run time (sec.):8910490 Total read(MB):8499 Total write(MB):0 Lifetime remaining: 99.844% Max bad block rate: 0.167% Health: OK Comment:NA No relevant entries about read/write errors in dmesg Also just copying 8G random data and reading those back gives a hash mismatch: root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock sha256sum test.dat read- 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s root@arbok:~# sha256sum test.dat read-back.dat 6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702253] Re: hio.ko driver from linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk
** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1702253 Title: hio.ko driver from linux- image-4.10.0-26-generic_4.10.0-26.30_amd64.deb will corrupt data on SSD disk Status in linux package in Ubuntu: Confirmed Bug description: The user upgrade Ubuntu server to linux- image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of ES3000 V2 SSD which the correspond module driver of hio.ko is include in this kernel. The data write to disk seems was incorrect. To format this sdd disk with xfs get error of "meta data corruption" and to use dd write data to this ssd disk and read out again, the sha256 chuksum is also mismatched. It was tested for 4.8.0-34-generic, 4.10.0-26-generic and 4.12, this problem was not found on 4.8.0-34-generic, but both 4.10.0-26-generic and 4.12 have same issues. This hio source can be download from http://support.huawei.com/enterprise/zh/server/es3000-v2-pid-21242728/software/22305278?idAbsPath=fixnode01%7C7919749%7C9856522%7C9856629%7C21462722%7C21242728. It is also include in Ubuntu kernel tree of linux-source-4.10.0. Huawei reports that they get similar problem when upgrading from linux4.4 to linux4.8 and they fix it at the hio driver in 2.1.0.28 version as: The modification for 4.8 is as below: if (!test_bit(SSD_ONLINE, >state)) { ssd_bio_endio(bio, -ENODEV); goto out; } #if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0)) blk_queue_split(q, , q->bio_split); #endif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
** Also affects: kexec-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in kexec-tools source package in Trusty: New Status in makedumpfile source package in Trusty: New Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Zesty: New Status in makedumpfile source package in Zesty: New Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is
[Kernel-packages] [Bug 1702223] Re: Surround (garbled) sound played to headset port
** 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/1702223 Title: Surround (garbled) sound played to headset port Status in linux package in Ubuntu: Incomplete Bug description: When using analog headset plugged into the audio port, sound is mono and processed so voice is silenced If played to speakers it works fine After killing pulseaudio at a bit of trouble, once can test using: speaker-test --channels 2 --nloops 1 --device plughw:PCH,0 which works fine for internal speakers, but is mono for headset If you watch youtube video, dialog is suppressed while other sounds may work This can be somewhat patched by going into alsamixer and set the left and right Headset channels to different levels using q/z and e/c keys This appears to be a bug in snd_hda_intel MacBook Air 2011 MacBookAir4,1 MacBook Air (11-inch, Mid 2011) chip: Cirrus 4206BCNZ 0:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) Subsystem: Intel Corporation Apple MacBookPro8,2 [Core i7, 15", 2011] [8086:7270] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic 4.10.0-22.24 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: foxyboy 21762 F...m pulseaudio /dev/snd/controlC0: foxyboy 21762 F pulseaudio CurrentDesktop: GNOME Date: Mon Jul 3 23:18:14 2017 HibernationDevice: RESUME=/dev/mapper/vg0-swap InstallationDate: Installed on 2015-10-28 (614 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Apple Inc. MacBookAir4,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-22-generic.efi.signed root=/dev/mapper/vg0-rfs ro RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-09 (86 days ago) dmi.bios.date: 06/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B12.1506081728 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B12.1506081728:bd06/08/2015:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702159] Re: Opal and POWER9 DD2
** 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/1702159 Title: Opal and POWER9 DD2 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: That will allow OPAL to configure the CPU in an optimal way. PATCH: http://patchwork.ozlabs.org/patch/783015/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1702159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702521] Re: cxlflash update request in the Xenial SRU stream
** 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/1702521 Title: cxlflash update request in the Xenial SRU stream Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Request to update cxlflash in the Xenial SRU stream There are multiple patches in upstream that are of interest and would like to see them pulled into the Xenial SRU stream. I have listed the patches that are in upstream/master tree. 41b99e1a30a6d04df7585905e5ffc7251099c6d3 scsi: cxlflash: Avoid mutex when destroying context 44ef38f9a2af8644c24ace6cbe1132dc70174c39 scsi: cxlflash: Cache owning adapter within context 888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 scsi: cxlflash: Add kref to context cd34af40a09c678abad36304eb68e1774640e908 scsi: cxlflash: Transition to application close model de9f0b0cbb86da288a2d38e35f2953a85608a6aa scsi: cxlflash: Remove adapter file descriptor cache 9442c9b0ed5c6f3a86dce0d6f714ef43f7f6cd53 scsi: cxlflash: Update documentation f80132613d576e7e705344d0c33f3b5e65d9e16a scsi: cxlflash: Refactor WWPN setup c4a11827b760ef8dcda26b5731d072b1d8fb7c81 scsi: cxlflash: Fix context reference tracking on detach 68ab2d76e4be785a7003fdb42b7c4ed8bba56ae2 scsi: cxlflash: Set sg_tablesize to 1 instead of SG_NONE 8a2605430a64bdf0361af5a18043717a2c59972f scsi: cxlflash: Fix crash in cxlflash_restore_luntable() 3d2f617d448f5e1d15d2844b803c13763ed51f1f scsi: cxlflash: Improve context_reset() logic 11f7b1844ac01d0298aad6a0ec2591bef4a1c3a2 scsi: cxlflash: Avoid command room violation e7ab2d401dbf633eaafe5bd1f39e84492848668f scsi: cxlflash: Remove unused buffer from AFU command 350bb478f57387df1e0b830fc64be2d1c3d55b6b scsi: cxlflash: Allocate memory instead of using command pool for AFU sync 5fbb96c8f1ba89fb220efb7e4eeed7cb5112becd scsi: cxlflash: Use cmd_size for private commands 25bced2b61b43b6372a73008dafa2183c5d53c39 scsi: cxlflash: Remove private command pool de01283baa334b1d938cfd9121198c517ad6dc89 scsi: cxlflash: Wait for active AFU commands to timeout upon tear down 9ba848acbf4fbc6d99a0992df9ef5eb1b4842ba9 scsi: cxlflash: Remove AFU command lock d4ace35166e55e73afe72a05d166342996063d35 scsi: cxlflash: Cleanup send_tmf() 9d89326c6660bc287b74983b51239460da10e189 scsi: cxlflash: Cleanup queuecommand() 48b4be36edf8a2cb0dedcb2d28f598e51249e805 scsi: cxlflash: Migrate IOARRIN specific routines to function pointers fe7f96982a4e7103ffab45fba34c57ee19b62639 scsi: cxlflash: Migrate scsi command pointer to AFU command 9c7d1ee5f13a7130f6d3df307ec010e9e003fa98 scsi: cxlflash: Refactor context reset to share reset logic 696d0b0c715360ce28fedd3c8b009d3771a5ddeb scsi: cxlflash: Support SQ Command Mode fb67d44dfbdf85d984b9b40284e90636a3a7b21d scsi: cxlflash: Cleanup prints 0df5bef739601f18bffc0d256ae451f239a826bd scsi: cxlflash: Cancel scheduled workers before stopping AFU 943445200b049d5179b95297e5372d399c8ab0e2 scsi: cxlflash: Enable PCI device ID for future IBM CXL Flash AFU 76a6ebbeef26b004c36a0c8ee0496bae5428fc31 scsi: cxlflash: Separate RRQ processing from the RRQ interrupt handler f918b4a8e6f8bb59c44045f85d10fd9cc7e5a4c0 scsi: cxlflash: Serialize RRQ access and support offlevel processing cba06e6de4038cd44a3e93a92ad982c372b8a14e scsi: cxlflash: Implement IRQ polling for RRQ processing 3b225cd32a05b627a6ca366f364a824beaabecc5 scsi: cxlflash: Update sysfs helper routines to pass config structure 78ae028e823701148e4915759459ee79597ea8ec scsi: cxlflash: Support dynamic number of FC ports 8fa4f1770d56af6f0a5a862f1fd298a4eeea94f3 scsi: cxlflash: Remove port configuration assumptions 0aa14887c60c27e3385295ee85f5ac079ae2ffb5 scsi: cxlflash: Hide FC internals behind common access routine 565180723294b06b3e60030033847277b9d6d4bb scsi: cxlflash: SISlite updates to support 4 ports 1cd7fabc82eb06c834956113ff287f8848811fb8 scsi: cxlflash: Support up to 4 ports 323e33428ea23bfb1ae5010b18b4540048b2ad51 scsi: cxlflash: Fence EEH during probe 50b787f7235efbd074bbdf4315e0cc261d85b4d7 scsi: cxlflash: Remove unnecessary DMA mapping cd41e18daf1a21fea5a195a5a74c97c6b183c15a scsi: cxlflash: Fix power-of-two validations fcc87e74a987dc9c0c85f53546df944ede76486a scsi: cxlflash: Fix warnings/errors e2ef33fa5958c51ebf0c6f18db19fe927e2185fa scsi: cxlflash: Improve asynchronous interrupt processing bfc0bab172cabf3bb25c48c4c521b317ff4a909d scsi: cxlflash: Support multiple hardware queues 3065267a80c88d775e8eb34196280e8eee33322f scsi: cxlflash: Add hardware queues attribute 1dd0c0e4fd02dc5e5bfaf89bd4656aabe4ae3cb3 scsi: cxlflash: Introduce hardware queue steering The patches are required on 16.04.3 HWE v4.10 kernel. I also have one more patch that we would like pulled into 16.04 SRU (HWE v4.10 kernel).
Re: [Kernel-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs
On 07/05/2017 08:14 PM, Daniel Axtens wrote: > Hi Tyler, > > Do you know what the changes between the ga-16.04 and hwe-16.04 kernel > are that make apparmor+overlayfs work? No, we're not currently aware of any code changes that would cause the behavioral change that is reported in the bug. Now that we have the specific kernel version of the HWE kernel, John Johansen can look into possible causes for the change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Incomplete Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702159] Re: Opal and POWER9 DD2
Patch sent to kernel-team mailing list: https://lists.ubuntu.com/archives/kernel-team/2017-July/085402.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/1702159 Title: Opal and POWER9 DD2 Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: That will allow OPAL to configure the CPU in an optimal way. PATCH: http://patchwork.ozlabs.org/patch/783015/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1702159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702323] Re: update-initramfs hangs
Hi, I'm in a loop. I try to run 'apport-collect 1702323' as instructed and I get a message saying I need to run 'apt-get install python-apport'. I run 'apt-get install python-apport' and I get a message saying dpkg was interrupted run 'dpkg --configure -a' I run 'dpkg --configure -a' and it hangs on 'update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic' It will stay like this forever so I have to crash out of this and an unable to do any updates. Any advice is gratefully welcomed. Kind regards Max ** 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/1702323 Title: update-initramfs hangs Status in linux package in Ubuntu: Confirmed Bug description: I have a server running version 16.04.1 LTS and kernel 4.4.0-62-generic I ran apt-get upgrade and the upgrade process hangs on... update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic In a separate shell I have tried update-initramfs -u -v and the process stops on "Calling hook cryptroot" In my /boot/ directory I now have a file initrd.img-4.4.0-83-generic.new which is 0Kb in size. I do not have any encrypted volumes. Please can you suggest how I can get round this error and complete the upgrade. Many thanks Max To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
** Changed in: kexec-tools (Ubuntu) Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu) Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis) ** Changed in: kexec-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: makedumpfile (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Bug description: == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see > http://pastebin.hursley.ibm.com/8239 > > I'm still investigating to figure out what is the reason behind this > behavior. > > Thanks, > > -- > maurosr That would smell like an out of memory condition that is alleviated with a smaller number of CPUs allowed for the kernel (so the amount of memory associated with per-CPU stuff is less in total). Per the bug description, the memory reserved for the crashkernel is 512MB: (In reply to comment #23) > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg That seems low for Power guests/systems. I think it theory is doesn't seem so, but the reality is that _for some reason(s)_ we require just too much memory to load and boot a kernel/initramfs (either on boot or kdump). When working w/
[Kernel-packages] [Bug 1701316] Re: Data corruption with hio driver
** Changed in: linux (Ubuntu) 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/1701316 Title: Data corruption with hio driver Status in linux package in Ubuntu: Confirmed Bug description: We are seeing data corruption issues using the hio driver with kernel 4.10.0 # uname -a Linux arbok 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Making xfs fails: root@arbok:~# mkfs.xfs /dev/hioa meta-data=/dev/hioa isize=512agcount=4, agsize=48835584 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=195342336, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=95382, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 bad magic number bad magic number Metadata corruption detected at xfs_sb block 0x0/0x200 libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200 The drive appears to be healthy. Firmware has been upgraded to ver 656: root@arbok:~# hio_info -d /dev/hioa hioaSerial number: 022XWV10G2000325 Size(GB): 800 Max size(GB): 800 Hardware version: 1.0 Firmware version: 656 Driver version: 2.1.0.28 Work mode: MLC Run time (sec.):8910490 Total read(MB):8499 Total write(MB):0 Lifetime remaining: 99.844% Max bad block rate: 0.167% Health: OK Comment:NA No relevant entries about read/write errors in dmesg Also just copying 8G random data and reading those back gives a hash mismatch: root@arbok:~# dd if=/dev/urandom of=test.dat bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 85.6076 s, 100 MB/s root@arbok:~# dd if=test.dat of=/dev/hioa bs=1G count=8 iflag=fullblock 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 10.6034 s, 810 MB/s root@arbok:~# dd if=/dev/hioa of=read-back.dat bs=1G count=8 iflag=fullblock sha256sum test.dat read- 8+0 records in 8+0 records out 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 66.1872 s, 130 MB/s root@arbok:~# sha256sum test.dat read-back.dat 6376d245a07c42c990589a3c17c44e63d826d1cb583fc5a065deff9dae69fd3a test.dat ebfb4ef19ae410f190327b5ebd312711263bc7579970e87d9c1e2d84e06b3c25 read-back.dat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702221] Re: Get spammed by PCIe Bus Error
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.12 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.12 ** 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/1702221 Title: Get spammed by PCIe Bus Error Status in linux package in Ubuntu: Incomplete Bug description: I'm spammed by PCIe Bus Error. I get this error 10 times per second in console. Error is: pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) device [8086:a112] error status/mask=0001/ pcieport :00:1c.0: [ 0] Receiver Error (First) I collected some sys info: lspci -vt>lspci_vt.log lspci -nnv>lspci_nnv.log lscpu>lscpu.log cat /proc/cpuinfo >proc_cpuinfo.log uname -a>uname_a.log lshw>lshw.log lsusb -v>lsusb_v.log dmidecode>dmidecode.log lsb_release -a>lsb_release.log iwconfig >iwconfig.log I run latest Ubuntu 17.04 on VivoBook Pro N752VX notebook (https://www.asus.com/Laptops/VivoBook-Pro-N752VX/specifications/). This pcieport 1c.0 is connected to RTL8192EE PCIe Wireless Network Adapter (see lspci_vt.log). I can disable this message by adding pci=nomsi kernel parameter, but this is not a bug fix, only a workaround. Also after appling this parameter wifi connection is quite slow and unstable. On windows 10 I get approx ping time 3ms to my wifi router. On Linux ping time is min/avg/max 5.548/60.137/261.145 with very good signal strength (see iwconfig.log). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmoukhataev 1907 F pulseaudio CurrentDesktop: XFCE Date: Tue Jul 4 08:33:04 2017 InstallationDate: Installed on 2017-05-18 (46 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. N752VX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=1365c792-1a17-47ad-8c37-f738d0645d3d ro nosplash pci=nomsi RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N752VX.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N752VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N752VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83
I don't know if this helps but I also have Kubuntu 16.04.2 installed on the same machine with: uname -a Linux aes-Inspiron-15-3567 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and wifi is working out-of-the-box on that. If you still want me to test with the kernel you've suggested, could you please explain how I could install 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/1702685 Title: No wifi connectivity with kernel 4.4.0-83 Status in linux package in Ubuntu: Incomplete Bug description: I have wifi connectivity with the previous kernel if I choose it from the GRUB screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasa1 2000 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) CurrentDesktop: Unity Date: Thu Jul 6 18:21:07 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=087adc85-f179-4429-9373-e2227f37cb9a InstallationDate: Installed on 2017-01-02 (185 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=30e6bdd2-27bf-4ef2-8076-333d24f18336 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in linux source package in Trusty: Invalid Status in makedumpfile source package in Trusty: New Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Zesty: Invalid Status in makedumpfile source package in Zesty: New Bug description: Problem Description == On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox. root@talclp1:~# echo c> /proc/sysrq-trigger [ 132.643690] sysrq: SysRq : Trigger a crash [ 132.643739] Unable to handle kernel paging request for data at address 0x [ 132.643745] Faulting instruction address: 0xc05c28f4 [ 132.643749] Oops: Kernel access of bad area, sig: 11 [#1] [ 132.643753] SMP NR_CPUS=2048 NUMA pSeries [ 132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod [ 132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic #16-Ubuntu [ 132.643824] task: c00111767080 task.stack: c000d82e [ 132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: c05c28c0 [ 132.643832] REGS: c000d82e3990 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 132.643836] MSR: 80009033CR: 28242422 XER: 0001 [ 132.643848] CFAR: c00087d0 DAR: DSISR: 4200 SOFTE: 1 GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063 GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998 GPR08: 0007 0001 0001 GPR12: c05c28c0 c7b4b900 2200 GPR16: 10170dc8 01002b566368 10140f58 100c7570 GPR20: 1017dd58 10153618 1017b608 GPR24: 3e87a294 0001 c0ebff60 0004 GPR28: c0ec0320 0063 c0e72a90 [ 132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50 [ 132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643914] Call Trace: [ 132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 (unreliable) [ 132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280 [ 132.643928] [c000d82e3cd0] [c05c4188] write_sysrq_trigger+0x78/0xa0 [ 132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110 [ 132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0 [ 132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240 [ 132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110 [ 132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108 [ 132.643961] Instruction dump: [ 132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 3949ba60 [ 132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 e8010010 7c0803a6 [ 132.643981] ---[ end trace eed6bbcd2c3bdfdf ]--- [ 132.646105] [ 132.646176] Sending IPI to other CPUs [ 132.647490] IPI complete I'm in purgatory -> smp_release_cpus() spinning_secondaries = 104 <- smp_release_cpus() [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through [2.739122] sd 1:2:3:0: [sdl] Assuming drive cache: write through [2.739123] sd 1:2:2:0: [sdk] Assuming drive cache: write through [
[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
This is a regression, we did lots of work a year ago to ensure the daemons handle bouncing integration services settings. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 607617] Re: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build
** Attachment removed: "F1E0501E6C0A1AAEC9C4F1E0B65DDB32.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4903807/+files/F1E0501E6C0A1AAEC9C4F1E0B65DDB32.jpg ** Attachment removed: "45DBEF267CE3FB0A84F23E4348AC40A2.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4905330/+files/45DBEF267CE3FB0A84F23E4348AC40A2.jpg ** Attachment removed: "2CE4BE4B3F86CC18B0D128CFC2C63E1D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4905983/+files/2CE4BE4B3F86CC18B0D128CFC2C63E1D.jpg ** Attachment removed: "85A8FCC9239F457FB939CA104B27A21F.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4887523/+files/85A8FCC9239F457FB939CA104B27A21F.jpg ** Attachment removed: "A78D60C6C8427CD36C0F60D8F7A81AF0.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4886018/+files/A78D60C6C8427CD36C0F60D8F7A81AF0.jpg ** Attachment removed: "BBDC246D19C63DA7C5580A8F1AFE7BD9.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4881658/+files/BBDC246D19C63DA7C5580A8F1AFE7BD9.jpg ** Attachment removed: "470585DE194D6FB6A958ED9875601C8D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4879722/+files/470585DE194D6FB6A958ED9875601C8D.jpg ** Attachment removed: "8A1B4741D6FB6CB2DE8EC1E0196498D9.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876291/+files/8A1B4741D6FB6CB2DE8EC1E0196498D9.jpg ** Attachment removed: "595D6BD8A6F070D990872C0BB0327EB1.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876265/+files/595D6BD8A6F070D990872C0BB0327EB1.jpg ** Attachment removed: "772C1B02BBB4C96A8C191CA3669D26D4.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4876190/+files/772C1B02BBB4C96A8C191CA3669D26D4.jpg ** Attachment removed: "DACC6012AFBAAE0509AFE41F6AB63C73.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4872082/+files/DACC6012AFBAAE0509AFE41F6AB63C73.jpg ** Attachment removed: "3AE5452A6D54CB9624801F9952714E4D.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4874798/+files/3AE5452A6D54CB9624801F9952714E4D.jpg ** Attachment removed: "image001.jpg" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+attachment/4777634/+files/image001.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/607617 Title: package bcmwl-kernel-source 5.60.48.36 bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Lucid: Won't Fix Status in bcmwl source package in Natty: Fix Released Bug description: My system is a Dell Vostro 1320 on which I installed the Broadcom wireless network driver after I had installed Ubuntu 10.04 LTS. I received this error when I tried to install the "flashplugin-installer" from the Synaptic Package Manager. I also tried to run the Flash Player Install from the Adobe web page and that also failed. I selected the "APT for Ubuntu 9.04+" and then pressed the "Agree and Install Now" button. I expected the Flash player to be installed as a plugin for Firefox but it fails to complete. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 Architecture: amd64 Date: Tue Jul 20 02:15:57 2010 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) PackageVersion: 5.60.48.36+bdcom-0ubuntu3 SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.60.48.36+bdcom-0ubuntu3 failed to install/upgrade: bcmwl kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/607617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp