[Kernel-packages] [Bug 1715063] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1715063 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715063 Title: ubuntu_blktrace_smoke_test failed with Trusty kernel Status in linux package in Ubuntu: Incomplete Bug description: ubuntu_blktrace_smoke_test failed with: Running '/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh' PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-3.13.0-130-generic) FAILED (cannot mkfs test loop image) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715064] 10/10: powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline
Default Comment by Bridge ** Attachment added: "10/10: powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline" https://bugs.launchpad.net/bugs/1715064/+attachment/4944499/+files/0010-powerpc-powernv-Clear-LPCR-PECE1-via-stop-api-only-f.patch ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715064 Title: 17.10 fails to boot on POWER9 DD2.0 with Deep stop states Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ranjal G. Shenoy On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the 17.10 kernel Ubuntu-4.12.0-12.13 fails to boot. It requires the following upstream fixes to be backported. 1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize core_idle_state_ptr") 2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & Per-core SPRs restore") 3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from deep-stop") 4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle states via stop API.") 5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for restoring state on P9 DD1") 6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't stop time") 7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT states when stop-api fails") 8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for stop4 cpuidle") 9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug") 10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline") Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in powerpc/linux.git -next branch. and 10) is posted upstream which fixes 9). These patches have been backported on top of Ubuntu-4.12.0-12.13 and tested on Boston where they are working as expected. == Comment: #1 - Ranjal G. Shenoy The lower 8 bits of core_idle_state_ptr tracks the number of non-idle threads in the core. This is supposed to be initialized to bit-map corresponding to the threads_per_core. However, currently it is initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for POWER8 which has 8 threads per core, but not for POWER9 which has 4 threads per core. As a result, on POWER9, core_idle_state_ptr gets initialized to 0xFF. In case when all the threads of the core are idle, the bits corresponding tracking the idle-threads are non-zero. As a result, the idle entry/exit code fails to save/restore per-core hypervisor state since it assumes that there are threads in the cores which are still active. Fix this by correctly initializing the lower bits of the core_idle_state_ptr on the basis of threads_per_core. Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize core_idle_state_ptr") == Comment: #2 - Ranjal G. Shenoy On POWER8, in case of - nap: both timebase and hypervisor state is retained. - fast-sleep: timebase is lost. But the hypervisor state is retained. - winkle: timebase and hypervisor state is lost. Hence, the current code for handling exit from a idle state assumes that if the timebase value is retained, then so is the hypervisor state. Thus, the current code doesn't restore per-core hypervisor state in such cases. But that is no longer the case on POWER9 where we do have stop states in which timebase value is retained, but the hypervisor state is lost. So we have to ensure that the per-core hypervisor state gets restored in such cases. Fix this by ensuring that even in the case when timebase is retained, we explicitly check if we are waking up from a deep stop that loses per-core hypervisor state (indicated by cr4 being eq or gt), and if this is the case, we restore the per-core hypervisor state. Cherry-picked from commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & Per-core SPRs restore") == Comment: #3 - Ranjal G. Shenoy On wakeup from a deep stop state which is supposed to lose the hypervisor state, we don't restore the LPCR to the old value but set it to a "sane" value via cur_cpu_spec->cpu_restore(). The problem is that the "sane" value doesn't include UPRT and the HR bits which are required to run correctly in Radix mode. Fix this on POWER9 onwards by restoring the LPCR value whatever it was before executin
[Kernel-packages] [Bug 1715063] [NEW] ubuntu_blktrace_smoke_test failed with Trusty kernel
Public bug reported: ubuntu_blktrace_smoke_test failed with: Running '/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh' PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-3.13.0-130-generic) FAILED (cannot mkfs test loop image) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Colin Ian King (colin-king) Status: New ** Tags: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715063 Title: ubuntu_blktrace_smoke_test failed with Trusty kernel Status in linux package in Ubuntu: New Bug description: ubuntu_blktrace_smoke_test failed with: Running '/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh' PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-3.13.0-130-generic) FAILED (cannot mkfs test loop image) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715064] [NEW] 17.10 fails to boot on POWER9 DD2.0 with Deep stop states
You have been subscribed to a public bug: == Comment: #0 - Ranjal G. Shenoy On Boston DD2.0 system, where deep stop states such as stop4 are enabled, the 17.10 kernel Ubuntu-4.12.0-12.13 fails to boot. It requires the following upstream fixes to be backported. 1) commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize core_idle_state_ptr") 2) commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & Per-core SPRs restore") 3) commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from deep-stop") 4) commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle states via stop API.") 5) commit 22c6663dc69a ("powerpc/powernv/idle: Use Requested Level for restoring state on P9 DD1") 6) commit f9122ee4f558 ("cpuidle-powernv: Allow Deep stop states that don't stop time") 7) commit 785a12afdb4a ("powerpc/powernv/idle: Disable LOSE_FULL_CONTEXT states when stop-api fails") 8) commit e1c1cfed5432 ("powerpc/powernv: Save/Restore additional SPRs for stop4 cpuidle") 9) commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug") 10) https://patchwork.ozlabs.org/patch/808233/ ("powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline") Of these 1-7 are in Linux Kernel 4.13. 8 and 9 are in powerpc/linux.git -next branch. and 10) is posted upstream which fixes 9). These patches have been backported on top of Ubuntu-4.12.0-12.13 and tested on Boston where they are working as expected. == Comment: #1 - Ranjal G. Shenoy The lower 8 bits of core_idle_state_ptr tracks the number of non-idle threads in the core. This is supposed to be initialized to bit-map corresponding to the threads_per_core. However, currently it is initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for POWER8 which has 8 threads per core, but not for POWER9 which has 4 threads per core. As a result, on POWER9, core_idle_state_ptr gets initialized to 0xFF. In case when all the threads of the core are idle, the bits corresponding tracking the idle-threads are non-zero. As a result, the idle entry/exit code fails to save/restore per-core hypervisor state since it assumes that there are threads in the cores which are still active. Fix this by correctly initializing the lower bits of the core_idle_state_ptr on the basis of threads_per_core. Cherry-picked from commit 5f221c3ca13d ("powerpc/powernv/idle: Correctly initialize core_idle_state_ptr") == Comment: #2 - Ranjal G. Shenoy On POWER8, in case of - nap: both timebase and hypervisor state is retained. - fast-sleep: timebase is lost. But the hypervisor state is retained. - winkle: timebase and hypervisor state is lost. Hence, the current code for handling exit from a idle state assumes that if the timebase value is retained, then so is the hypervisor state. Thus, the current code doesn't restore per-core hypervisor state in such cases. But that is no longer the case on POWER9 where we do have stop states in which timebase value is retained, but the hypervisor state is lost. So we have to ensure that the per-core hypervisor state gets restored in such cases. Fix this by ensuring that even in the case when timebase is retained, we explicitly check if we are waking up from a deep stop that loses per-core hypervisor state (indicated by cr4 being eq or gt), and if this is the case, we restore the per-core hypervisor state. Cherry-picked from commit ec4867355244 ("powerpc/powernv/idle: Decouple Timebase restore & Per-core SPRs restore") == Comment: #3 - Ranjal G. Shenoy On wakeup from a deep stop state which is supposed to lose the hypervisor state, we don't restore the LPCR to the old value but set it to a "sane" value via cur_cpu_spec->cpu_restore(). The problem is that the "sane" value doesn't include UPRT and the HR bits which are required to run correctly in Radix mode. Fix this on POWER9 onwards by restoring the LPCR value whatever it was before executing the stop instruction. Cherry-picked from commit cb0be7ec0307 ("powerpc/powernv/idle: Restore LPCR on wakeup from deep-stop") == Comment: #4 - Ranjal G. Shenoy Some of the SPR values (HID0, MSR, SPRG0) don't change during the run time of a booted kernel, once they have been initialized. The contents of these SPRs are lost when the CPUs enter deep stop states. So instead saving and restoring SPRs from the kernel, use the stop-api provided by the firmware by which the firmware can restore the contents of these SPRs to their initialized values after wakeup from a deep stop state. Apart from these, program the PSSCR value to that of the deepest stop state via the stop-api. This will be used to indicate to the underlying firmware as to what stop state to
[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))
I don't have a special wireless off/on button on my keyboard but I'm assuming rfkill will do (soft kill switch). The issue does not get triggered by the following loop (I may leave it for several hours to get a better picture and modify to wait more intelligently): ➜ ~ while test 1 ; do rfkill block 1 ; sleep 10 ; rfkill unblock 1 ; sleep 10 ; done сен 05 01:26:13 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee by local choice (Reason: 3=DEAUTH_LEAVING) сен 05 01:26:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:29 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:29 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee сен 05 01:26:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:26:29 blade kernel: wlp59s0: authenticated сен 05 01:26:29 blade kernel: wlp59s0: associate with 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:26:29 blade kernel: wlp59s0: RX AssocResp from 18:d6:c7:b0:26:ee (capab=0x431 status=0 aid=1) сен 05 01:26:29 blade kernel: wlp59s0: associated сен 05 01:26:29 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready сен 05 01:26:33 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee by local choice (Reason: 3=DEAUTH_LEAVING) сен 05 01:26:44 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:44 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:49 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:26:49 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee сен 05 01:26:49 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:26:49 blade kernel: wlp59s0: authenticated сен 05 01:26:49 blade kernel: wlp59s0: associate with 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:26:49 blade kernel: wlp59s0: RX AssocResp from 18:d6:c7:b0:26:ee (capab=0x431 status=0 aid=1) сен 05 01:26:49 blade kernel: wlp59s0: associated сен 05 01:26:49 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready сен 05 01:26:53 blade kernel: wlp59s0: deauthenticating from 18:d6:c7:b0:26:ee by local choice (Reason: 3=DEAUTH_LEAVING) сен 05 01:27:04 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:04 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:09 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:09 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 2/3) сен 05 01:27:09 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 3/3) сен 05 01:27:09 blade kernel: wlp59s0: authentication with 18:d6:c7:b0:26:ee timed out сен 05 01:27:10 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38 сен 05 01:27:10 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3) сен 05 01:27:10 blade kernel: wlp59s0: authenticated сен 05 01:27:10 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3) сен 05 01:27:10 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=4) сен 05 01:27:10 blade kernel: wlp59s0: associated сен 05 01:27:10 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready сен 05 01:27:14 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING) сен 05 01:27:24 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:25 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:29 blade kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready сен 05 01:27:29 blade kernel: wlp59s0: authenticate with 18:d6:c7:b0:26:ee сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 1/3) сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 2/3) сен 05 01:27:29 blade kernel: wlp59s0: send auth to 18:d6:c7:b0:26:ee (try 3/3) сен 05 01:27:29 blade kernel: wlp59s0: authentication with 18:d6:c7:b0:26:ee timed out сен 05 01:27:30 blade kernel: wlp59s0: authenticate with d8:74:95:e5:88:38 сен 05 01:27:30 blade kernel: wlp59s0: send auth to d8:74:95:e5:88:38 (try 1/3) сен 05 01:27:30 blade kernel: wlp59s0: authenticated сен 05 01:27:30 blade kernel: wlp59s0: associate with d8:74:95:e5:88:38 (try 1/3) сен 05 01:27:30 blade kernel: wlp59s0: RX AssocResp from d8:74:95:e5:88:38 (capab=0x411 status=0 aid=4) сен 05 01:27:30 blade kernel: wlp59s0: associated сен 05 01:27:30 blade kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready сен 05 01:27:34 blade kernel: wlp59s0: deauthenticating from d8:74:95:e5:88:38 by local choice (Reason: 3=DEAUTH_LEAVING) сен 05 01:27:44 blade kernel: usb 1-1: USB disconnect, de
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
I've come across an interesting development regarding the Touchpad issue. Since I was having the random freeze when logging in after stand by (or just locked screen), I decided to switch from gdm to lightdm to see if that solves the issue. Indeed, I no longer experience any freezing when logging in. However, the Touchpad now never works even after returning from standby. To add to that, I also noticed that when gdm was freezing and I had to restart it, the Touchpad stops working afterwards (and I usually had to go to standby and back to make it work again). Seems that there's a direct relation between gdm and the Touchpad. Not sure what though. -- You 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/inp
[Kernel-packages] [Bug 1715051] 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/1715051 Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-libc-dev:amd64 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yash 1710 F pulseaudio Date: Tue Sep 5 08:44:43 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-09-05 08:43:58 Commandline: /usr/bin/unattended-upgrade Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic) Upgrade: python3-jwt:amd64 (1.3.0-1, 1.3.0-1ubuntu0.1), linux-image-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), liblouis9:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), python3-louis:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.78-0ubuntu0.16.04.1293, 60.0.3112.113-0ubuntu0.16.04.1298), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), liblouis-data:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-headers-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35) DuplicateSignature: package:linux-libc-dev:amd64:4.4.0-93.116 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package linux-libc-dev:amd64 (--configure): package linux-libc-dev:amd64 is not ready for configuration ErrorMessage: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2b605a61-78e4-48e2-b997-b7b02b7855d6 InstallationDate: Installed on 2017-08-29 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7592 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 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 2.02~beta2-36ubuntu3.12 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P26 (MS-7592) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.8:bd08/26/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 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
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Expired 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 1715051] Re: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'h
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715051 Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-libc-dev:amd64 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yash 1710 F pulseaudio Date: Tue Sep 5 08:44:43 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-09-05 08:43:58 Commandline: /usr/bin/unattended-upgrade Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic) Upgrade: python3-jwt:amd64 (1.3.0-1, 1.3.0-1ubuntu0.1), linux-image-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), liblouis9:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), python3-louis:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.78-0ubuntu0.16.04.1293, 60.0.3112.113-0ubuntu0.16.04.1298), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), liblouis-data:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-headers-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35) DuplicateSignature: package:linux-libc-dev:amd64:4.4.0-93.116 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package linux-libc-dev:amd64 (--configure): package linux-libc-dev:amd64 is not ready for configuration ErrorMessage: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2b605a61-78e4-48e2-b997-b7b02b7855d6 InstallationDate: Installed on 2017-08-29 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7592 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 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 2.02~beta2-36ubuntu3.12 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P26 (MS-7592) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.8:bd08/26/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715051] [NEW] package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-libc-dev:amd64 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yash 1710 F pulseaudio Date: Tue Sep 5 08:44:43 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-09-05 08:43:58 Commandline: /usr/bin/unattended-upgrade Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic) Upgrade: python3-jwt:amd64 (1.3.0-1, 1.3.0-1ubuntu0.1), linux-image-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), liblouis9:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), python3-louis:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.78-0ubuntu0.16.04.1293, 60.0.3112.113-0ubuntu0.16.04.1298), xserver-xorg-core-hwe-16.04:amd64 (2:1.18.4-1ubuntu6.1~16.04.1, 2:1.18.4-1ubuntu6.1~16.04.2), liblouis-data:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-headers-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35) DuplicateSignature: package:linux-libc-dev:amd64:4.4.0-93.116 Processing triggers for libc-bin (2.23-0ubuntu9) ... dpkg: error processing package linux-libc-dev:amd64 (--configure): package linux-libc-dev:amd64 is not ready for configuration ErrorMessage: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=2b605a61-78e4-48e2-b997-b7b02b7855d6 InstallationDate: Installed on 2017-08-29 (6 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: MSI MS-7592 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic 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 2.02~beta2-36ubuntu3.12 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P26 (MS-7592) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.8:bd08/26/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-P26(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1715051 Title: package linux-libc-dev:amd64 4.4.0-93.116 failed to install/upgrade: package linux-libc-dev:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-libc-dev:amd64 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yash 1710 F pulseaudio Date: Tue Sep 5 08:44:43 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-09-05 08:43:58 Commandline: /usr/bin/unattended-upgrade Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic) Upgrade: python3-jwt:amd64 (1.3.0-1, 1.3.0-1ubuntu0.1), linux-image-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), liblouis9:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), linux-generic-hwe-16.04:amd64 (4.8.0.36.8, 4.10.0.33.35), python3-louis:amd64 (2.6.4-2, 2.6.4-2ubuntu0.1), chromium-codecs-ffmpeg-e
[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker
4.10.0-34.38 - generic Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in amd64: hwclock - failed on lodygin only, bug 1714229 monotonic_time - gtod failed on fozzie, gtod, tsc failed on lodygin ubuntu_kvm_unit_tests - smap, pku and svm failed ubuntu_unionmount_overlayfs_suite - only failed on rumford, passed on other nodes ubuntu_zfs_xfs_generic - 192 failed on rumford, passed after re-run xfstests - btrfs, xfs failed Issue to note in arm64: rtc - Update IRQs not supported on node wright hwclock - failed to change time ubuntu_bpf - failed to build, bug 1675395 ubuntu_kernel_selftests - breakpoint test failed to build, bug 1680507 ubuntu_zfs_xfs_generic - test 079, 317 failed (179 passed after re-test) Issue to note in i386: monotonic_time - gtod failed on rizzo ubuntu_bpf - test_maps bpf test crashed, bug 1711512 xfstests - btrfs, xfs failed, not regression Issue to note in ppc64le: libhugetlbfs - 4 failed, 7 killed by signal (small_const / small_data is not hugepage) rtc - Update IRQs not supported. ubuntu_kvm_unit_tests - ld: powerpc/selftest.elf: Not enough room for program headers xfstests - btrfs, xfs failed Issue to note in s390x (zKVM): aio_dio_bugs - event res -22, not regression libhugetlbfs - 10 failed, 7 killed by signal, 1 bad config, issue seen before scrashme - failed to build bug 1689240 ubuntu_bpf - failed to build, bug 1711299 ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed ubuntu_lxc - Failed to start networking in ubuntu-cloud container, passed after re-test ubuntu_qrt_apparmor - timed out, passed after re-test Issue to note in s390x (zVM): aio_dio_bugs - event res -22, not regression libhugetlbfs - IOError: [Errno 95] Operation not supported scrashme - failed to build bug 1689240 ubuntu_bpf - failed to build, bug 1711299 ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** 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/1713470 Title: linux: 4.10.0-34.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the 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 backports: 1713471,1713472 derivatives: 1713473 -- 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-sru-workflow/+bug/1713470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
I'm not sure that would help. A few people above have said that 17.04 is affected and 17.04 ships with PulseAudio 10.0 already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b 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: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Has anyone tried compiling/installing pulseaudio 9 to see if it resolves the bug as it seems to be present on multiple version of Ubuntu/derivatives and across multiple kernels? Just a thought. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b 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: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713462 Title: linux: 4.4.0-94.117 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 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 backports: 1713463 derivatives: 1713464,1713465,1713467,1713468,1713469 -- 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-sru-workflow/+bug/1713462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709784] Comment bridged from LTC Bugzilla
--- Comment From jos...@br.ibm.com 2017-09-04 20:46 EDT--- Only to let you know that I just tested this version successfully as well. Thanks! Jose Ziviani -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruction dump: [ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 340.182938] ---[ end trace bc5080cb7d18f102 ]--- [ 340.276202] This was with the latest ubuntu cloud image. I get the same thing when trying to use vir
[Kernel-packages] [Bug 1709784] Comment bridged from LTC Bugzilla
--- Comment From grom...@br.ibm.com 2017-09-04 19:23 EDT--- Hi jsalisbury, linux-image-4.4.0-94-generic from -proposed looks fine to me. VMs boot ok and as expected no TRAP 0xF60 (Facility Unavailable) in dmesg: root@sid:~# apt-get -t xenial-proposed install linux-image-4.4.0-94-generic root@sid:~# uname -a Linux sid 4.4.0-94-generic #117-Ubuntu SMP Tue Aug 29 08:13:18 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@sid:/# dmesg | fgrep 0f60 root@sid:/# virsh list IdName State 1 debian running 2 1604 running 4 unstable running root@sid:/# virsh console 2 Connected to domain 1604 Escape character is ^] Ubuntu 16.04.3 LTS 1604 hvc0 1604 login: ubuntu Password: Last login: Mon Aug 14 15:41:29 EDT 2017 from 10.1.0.1 on pts/0 Welcome to Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-30-generic ppc64le) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage You have new mail. 1604 ? ~ I understand that no further action from IBM is necessary now. Please, let me know if it's not true. BTW, do you know when this will likely reach the SRU? Thanks a lot and best regards, Gustavo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37b
[Kernel-packages] [Bug 1714420] Re: kernel oops - kvm guest started at boot time
** Description changed: + [SRU Justification] + + [Impact] + System OOPSes shortly after boot when KVM guests are started. + + [Fix] + Cherry-pick patch e47057151422a67ce08747176fa21cb3b526a2c9 + + [Testcase] + Tested at IBM - boot a machine with a KVM guest configured to start at boot. Without this patch, observe OOPS, with this patch, observe no OOPS. + + [Regression Potential] + Patch is contained in arch/powerpc; so regression potential limited to that arch. Patch accepted to kernel stable trees, suggesting others also believe it to be of low risk. + + [Original Report] + [0.00] Linux version 4.4.0-93-generic (buildd@bos01-ppc64el-025) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #116-Ubuntu SMP Fri Aug 11 16:30:16 UTC 2017 (Ubuntu 4.4.0-93.116-generic 4.4.79) ... [ 380.184554] KVM guest htab at c0799900 (order 29), LPID 2 [ 380.527576] Facility 'TM' unavailable, exception at 0xd0003aad7f10, MSR=90009033 [ 380.527717] Oops: Unexpected facility unavailable exception, sig: 6 [#2] [ 380.527775] SMP NR_CPUS=2048 NUMA PowerNV [ 380.527823] Modules linked in: vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 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 overlay binfmt_misc bridge stp llc kvm_hv uio_pdrv_genirq uio leds_powernv ipmi_powernv ibmpowernv vmx_crypto powernv_rng ipmi_msghandler kvm_pr kvm autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 raid10 ses enclosure mlx4_en be2net lpfc vxlan mlx4_core scsi_transport_fc ip6_udp_tunnel udp_tunnel ipr [ 380.528781] CPU: 24 PID: 4277 Comm: qemu-system-ppc Tainted: G D 4.4.0-93-generic #116-Ubuntu [ 380.528861] task: c3c389b0 ti: c01fb2428000 task.ti: c01fb2428000 [ 380.528929] NIP: d0003aad7f10 LR: d00037d52a14 CTR: d0003aad7e40 [ 380.528997] REGS: c01fb242b7b0 TRAP: 0f60 Tainted: G D (4.4.0-93-generic) [ 380.529076] MSR: 90009033 CR: 22024848 XER: [ 380.529247] CFAR: d0003aad7ea4 SOFTE: 1 -GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 c01fdbf6 -GPR04: c01f8580 c01fb242bbc0 -GPR08: 0001 c3c389b0 0001 d00037d578f8 -GPR12: d0003aad7e40 cfb4e400 001f -GPR16: 3fff7206 0080 3fff892c4390 3fff7285f200 -GPR20: 010009988430 0100099affd0 3fff7285eb60 100c1ff0 -GPR24: 3bcf4e10 3fff72040028 c01fdbf6 -GPR28: c01f8580 c01fdbf6 c01f8580 + GPR00: d00037d52a14 c01fb242ba30 d0003aaec018 c01fdbf6 + GPR04: c01f8580 c01fb242bbc0 + GPR08: 0001 c3c389b0 0001 d00037d578f8 + GPR12: d0003aad7e40 cfb4e400 001f + GPR16: 3fff7206 0080 3fff892c4390 3fff7285f200 + GPR20: 010009988430 0100099affd0 3fff7285eb60 100c1ff0 + GPR24: 3bcf4e10 3fff72040028 c01fdbf6 + GPR28: c01f8580 c01fdbf6 c01f8580 [ 380.530119] NIP [d0003aad7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 380.530188] LR [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 380.530245] Call Trace: [ 380.530270] [c01fb242ba30] [c01fb242bab0] 0xc01fb242bab0 (unreliable) [ 380.530353] [c01fb242bb70] [d00037d52a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 380.530436] [c01fb242bba0] [d00037d4f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 380.530519] [c01fb242bbe0] [d00037d43918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 380.530602] [c01fb242bd40] [c02fff60] do_vfs_ioctl+0x480/0x7d0 [ 380.530671] [c01fb242bde0] [c0300384] SyS_ioctl+0xd4/0xf0 [ 380.530742] [c01fb242be30] [c0009204] system_call+0x38/0xb4 [ 380.530837] Instruction dump: [ 380.530904] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 380.531126] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 380.531350] ---[ end trace 8f9b3b82f9a07d76 ]--- - - Needs kernel patch e47057151422a67ce0874
[Kernel-packages] [Bug 1686019] Comment bridged from LTC Bugzilla
--- Comment From jos...@br.ibm.com 2017-09-04 16:56 EDT--- Hello Kleber, I just tested the kernel in my Power9 system and it's working fine. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686019 Title: Ubuntu 16.04.3: Qemu fails on P9 Status in The Ubuntu-power-systems project: Fix Committed Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kernel-package source package in Zesty: New Status in linux source package in Zesty: Fix Committed Bug description: Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10 tree[1], I see the following error when trying to boot a 17.04 image. 8000 DISK : "QEMU QEMU HARDDISK2.5+" Populating /pci@8002000 No NVRAM common partition, re-initializing... Scanning USB Using default console: /vdevice/vty@7100 ted RAM kernel at 40 (17995b0 bytes) C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Booting from memory... OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8) Detected machine type: 0101 command line: debug initcall_debug udbg-immortal console=/dev/hvc0 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 01bb alloc_top: 1000 alloc_top_hi : 8000 rmo_top : 1000 ram_top : 8000 instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x041c -> 0x041c09fd Device tree struct 0x041d -> 0x041e Quiescing Open Firmware ... Booting Linux via __start() @ 0x0040 ... I tried to add some debug options as "debug initcall_debug udbg-immortal console=/dev/hvc0" but no luck. [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10 ---uname output--- 4.10.0-19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9
** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686019 Title: Ubuntu 16.04.3: Qemu fails on P9 Status in The Ubuntu-power-systems project: Fix Committed Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kernel-package source package in Zesty: New Status in linux source package in Zesty: Fix Committed Bug description: Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10 tree[1], I see the following error when trying to boot a 17.04 image. 8000 DISK : "QEMU QEMU HARDDISK2.5+" Populating /pci@8002000 No NVRAM common partition, re-initializing... Scanning USB Using default console: /vdevice/vty@7100 ted RAM kernel at 40 (17995b0 bytes) C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Booting from memory... OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8) Detected machine type: 0101 command line: debug initcall_debug udbg-immortal console=/dev/hvc0 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 01bb alloc_top: 1000 alloc_top_hi : 8000 rmo_top : 1000 ram_top : 8000 instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x041c -> 0x041c09fd Device tree struct 0x041d -> 0x041e Quiescing Open Firmware ... Booting Linux via __start() @ 0x0040 ... I tried to add some debug options as "debug initcall_debug udbg-immortal console=/dev/hvc0" but no luck. [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10 ---uname output--- 4.10.0-19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)
Status: Right now I'm on linux-image-generic-hwe-16.04 version 4.10.0.33.35 and it looks like the situation has improved a lot. The last few days I was able to suspend and resume and the fan remained silent. I only remember one time when the fan was loud and only a reboot helped. Therefore I'd like to keep this issue open for a few more days, just to see if it happens again... Besides this, I would still be happy if anyone can answer my questions from above... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711951 Title: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: This is a copy of a very similar bug report which is currently marked as triaged and where my comment is ignored maybe because of that. Please see my additional remarks at the end of this report. --- Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running Ubuntu 17.04 has its fan go full steam if the laptop is woken up from sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or silent, even for hours. The bug has been fixed upstream, see 6625914 ACPI / EC: Drop EC noirq hooks to fix a regression 9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129 (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181) and I hope this fix will make its way into a near-future kernel update to ubuntu :) Many thanks! --- Source: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709616 Additional remarks: - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 5th Gen. - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who run the HWE kernel on Ubuntu 16.04 LTS will have this problem too! I can reproduce it on my local system which has "linux-image-generic- hwe-16.04" installed (4.10.0.32.34). Reading through the comments, it's not exactly clear to me which of the commits has fixed this problem, but I guess that the following two changes have made the difference: https://patchwork.kernel.org/patch/9835823/ https://patchwork.kernel.org/patch/9835825/ I am reporting this as a new issue because the fixes from 4.13 need to be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715015] 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/1715015 Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Found during update: sudo apt-get install update-manager ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-83-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 4 16:01:35 2017 DuplicateSignature: package:linux-image-extra-3.13.0-83-generic:(not installed):package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=/dev/mapper/katelt--vg-swap_1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 2537WGY ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-83-generic root=/dev/mapper/hostname--vg-root ro splash quiet 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-9ubuntu1.14 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-08-22 (378 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET81WW (1.41 ) dmi.board.name: 2537WGY 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:bvr6IET81WW(1.41):bd02/09/2012:svnLENOVO:pn2537WGY:pvrThinkPadT410:rvnLENOVO:rn2537WGY:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537WGY dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715015] Re: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration ca
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715015 Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Found during update: sudo apt-get install update-manager ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-83-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 4 16:01:35 2017 DuplicateSignature: package:linux-image-extra-3.13.0-83-generic:(not installed):package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=/dev/mapper/katelt--vg-swap_1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 2537WGY ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-83-generic root=/dev/mapper/hostname--vg-root ro splash quiet 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-9ubuntu1.14 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-08-22 (378 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET81WW (1.41 ) dmi.board.name: 2537WGY 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:bvr6IET81WW(1.41):bd02/09/2012:svnLENOVO:pn2537WGY:pvrThinkPadT410:rvnLENOVO:rn2537WGY:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537WGY dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715015] [NEW] package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration
Public bug reported: Found during update: sudo apt-get install update-manager ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-83-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 4 16:01:35 2017 DuplicateSignature: package:linux-image-extra-3.13.0-83-generic:(not installed):package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=/dev/mapper/katelt--vg-swap_1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 2537WGY ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-83-generic root=/dev/mapper/hostname--vg-root ro splash quiet 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-9ubuntu1.14 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-08-22 (378 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET81WW (1.41 ) dmi.board.name: 2537WGY 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:bvr6IET81WW(1.41):bd02/09/2012:svnLENOVO:pn2537WGY:pvrThinkPadT410:rvnLENOVO:rn2537WGY:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2537WGY dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715015 Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Confirmed Bug description: Found during update: sudo apt-get install update-manager ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-83-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 4 16:01:35 2017 DuplicateSignature: package:linux-image-extra-3.13.0-83-generic:(not installed):package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=/dev/mapper/katelt--vg-swap_1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 2537WGY ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-83-generic root=/dev/mapper/hostname--vg-root ro splash quiet 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-9ubuntu1.14 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-83-generic (not installed) failed to install/upgrade: package linux-image-extra-3.13.0-83-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to trusty on 2016-08-22 (378 days ago) dmi.bios.date: 02/09/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET81WW (1.41 ) dmi.board.name: 2537WGY 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:bvr6IET81WW(1.4
[Kernel-packages] [Bug 1708130] Comment bridged from LTC Bugzilla
--- Comment From mauri...@br.ibm.com 2017-09-04 13:34 EDT--- Indira, thank you. Wendy, reassigning back to you for further analysis, as only Paul's patch was not sufficient to fix this problem on Ubuntu. (In reply to comment #45) > Started Leaf IO and BASE(without smt tests)and then tried to change the SMT > value using test script and ppc64 command hangs after few hours of > regression run. > Linux lotkvm 4.10.0-330-generic #37~16.04.1+bz156441 SMP Wed Aug 16 17:45:59 CDT 2017 ppc64le ppc64le ppc64le 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/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
[Kernel-packages] [Bug 1708130] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2017-09-04 13:26 EDT--- Hi Mauricio, Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value using test script and ppc64 command hangs after few hours of regression run. > root@lotkvm:/kte/tools/setup.d# show.report.py HOSTNAMEKERNEL VERSIONDISTRO INFO ----- lotkvm 4.10.0-330-genericUbuntu 16.04.3 LTS \n \l Current Time: Mon Sep 4 07:53:05 2017 Job-ID FOCUS Start-Time DurationFunction -- - -- 2 IO 20170904-06:36:31 1.0 hr(s) 16.0 min(s) IO_Focus 3 BASE 20170904-07:52:20 0.0 hr(s) 0.0 min(s)Test FOCUS IO BASESUM TOTAL 774 6 780 FAIL0 2 2 PASS774 4 778 (%) (100%) (66%) (99%) > Used below test script from the path lotkvm:/home/smtchange.sh to change SMT value periodically [ipjoga@kte tmp]$ cat smt* #!/bin/bash while true do ppc64_cpu --smt=2 echo "SMT changed to 2" date sleep 240 ppc64_cpu --smt=4 echo "SMT changed to 4" date sleep 240 ppc64_cpu --smt=8 echo "SMT changed to 8" date sleep 240 ppc64_cpu --smt=off echo "SMT changed to off" date sleep 240 done root@lotkvm:/home# nohup ./smtchange.sh & [1] 4604 root@lotkvm:/home# nohup: ignoring input and appending output to 'nohup.out' > Run went fine for few hours like 3 - 4 hours but after that seen ppc64 command hangs as below from the log root@lotkvm:/home# cat nohup.out SMT changed to 2 Mon Sep 4 07:54:02 CDT 2017 SMT changed to 4 Mon Sep 4 07:58:06 CDT 2017 SMT changed to 8 Mon Sep 4 08:02:16 CDT 2017 SMT changed to off Mon Sep 4 08:06:39 CDT 2017 SMT changed to 2 Mon Sep 4 08:10:40 CDT 2017 SMT changed to 4 Mon Sep 4 08:14:47 CDT 2017 SMT changed to 8 Mon Sep 4 08:18:56 CDT 2017 SMT changed to off Mon Sep 4 08:23:19 CDT 2017 SMT changed to 2 Mon Sep 4 08:27:22 CDT 2017 SMT changed to 4 Mon Sep 4 08:31:26 CDT 2017 SMT changed to 8 Mon Sep 4 08:35:36 CDT 2017 SMT changed to off Mon Sep 4 08:39:58 CDT 2017 SMT changed to 2 Mon Sep 4 08:44:02 CDT 2017 SMT changed to 4 Mon Sep 4 08:48:07 CDT 2017 SMT changed to 8 Mon Sep 4 08:52:17 CDT 2017 SMT changed to off Mon Sep 4 08:56:40 CDT 2017 SMT changed to 2 Mon Sep 4 09:00:42 CDT 2017 SMT changed to 4 Mon Sep 4 09:04:47 CDT 2017 SMT changed to 8 Mon Sep 4 09:09:02 CDT 2017 SMT changed to off Mon Sep 4 09:13:26 CDT 2017 SMT changed to 2 Mon Sep 4 09:17:29 CDT 2017 SMT changed to 4 Mon Sep 4 09:21:37 CDT 2017 SMT changed to 8 Mon Sep 4 09:25:46 CDT 2017 SMT changed to off Mon Sep 4 09:30:07 CDT 2017 SMT changed to 2 Mon Sep 4 09:34:09 CDT 2017 SMT changed to 4 Mon Sep 4 09:38:27 CDT 2017 SMT changed to 8 Mon Sep 4 09:42:42 CDT 2017 root@lotkvm:~# date Mon Sep 4 12:03:28 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt ^Z^X^C root@lotkvm:/home# ps -ef | grep ppc64* >root@lotkvm:~# uname -a Linux lotkvm 4.10.0-330-generic #37~16.04.1+bz156441 SMP Wed Aug 16 17:45:59 CDT 2017 ppc64le ppc64le ppc64le GNU/Linux root@lotkvm:~# uname -r 4.10.0-330-generic > System is available for debugging > Trying to get dmesg logs as console hangs after running ppc64 command Regards, Indira -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - INDIRA P. JOGA - 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0
[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => Incomplete ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: systemd (Ubuntu 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/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
I do not believe I can land the systemd change, unless 4.4 kernel picks up the above mentioned fix. As otherwise hwe kernels will work, and GA kernel will not. ** Changed in: systemd (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Canonical Kernel (canonical-kernel) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in systemd source package in Xenial: Incomplete Bug description: When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714193] Re: Enable ppc64el build
** Changed in: linux (Ubuntu) Status: In Progress => 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/1714193 Title: Enable ppc64el build Status in linux package in Ubuntu: Fix Released Bug description: Numatop now supports ppc64el functionality, however the packaging does not enable this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704720] Re: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11
** Changed in: linux (Ubuntu) Status: In Progress => 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/1704720 Title: ubuntu_lttng_smoke_test failed on Artful 4.11.0-11 Status in linux package in Ubuntu: Incomplete Bug description: After bug 1699755, this test was found failed on Artful again with kernel 4.11.0-11 $ dmesg | grep lttng [ 8282.279726] lttng_kretprobes: loading out-of-tree module taints kernel. [ 8282.279754] lttng_kretprobes: module verification failed: signature and/or required key missing - tainting kernel [ 8282.282192] lttng_tracer: Unknown symbol lttng_ftrace_unregister (err 0) [ 8282.282205] lttng_tracer: Unknown symbol lttng_ftrace_register (err 0) [ 8282.282216] lttng_tracer: Unknown symbol lttng_ftrace_destroy_private (err 0) $ sudo ./ubuntu_lttng_smoke_test.sh == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == Error: Unable to list kernel events: Kernel tracer not available Error: Command error FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event open: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event openat: Kernel tracer not available (channel channel0, session test-kernel-session) Error: Event close: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-13336-session PASSED (lttng create) Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: User Name 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 17 04:00 seq crw-rw 1 root audio 116, 33 Jul 17 04:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 17 06:22:17 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu18 --- zfs-linux (0.6.5.6-0ubuntu18) xenial; urgency=medium * Improve cloning performance for large numbers of clones (LP: #1567557) Bump zcmd buffer from 16K to 256K. * Correctly install libraries such as libnvpair.so.1 to /lib and not /usr/lib, this also fixes boot issues (LP: #1596835) -- Colin Ian King Fri, 11 Aug 2017 08:33:23 +0100 ** Changed in: zfs-linux (Ubuntu Xenial) Status: Fix Committed => 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/1567557 Title: Performance degradation of "zfs clone" Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU Justification] Creating tens of hundreds of clones can be prohibitively slow. The underlying mechanism to gather clone information is using a 16K buffer which limits performance. Also, the initial assumption is to pass in zero sized buffer to the underlying ioctl() to get an idea of the size of the buffer required to fetch information back to userspace. If we bump the initial buffer to a larger size then we reduce the need for two ioctl calls which improves performance. [Fix] Bump initial buffer size from 16K to 256K [Regression Potential] This is minimal as this is just a tweak in the initial buffer size and larger sizes are handled correctly by ZFS since they are normally used on the second ioctl() call once we have established the size of the buffer required from the first ioctl() call. Larger initial buffers just remove the need for the initial size estimation for most cases where the number of clones is less than ~5000. There is a risk that a larger buffer size could lead to a ENOMEM issue when allocating the buffer, but the size of buffer used is still trivial for modern large 64 bit servers running ZFS. [Test case] Create 4000 clones. With the fix this takes 35-40% less time than without the fix. See the example test.sh script as an example of how to create this many clones. -- I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged
[Kernel-packages] [Bug 1567557] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1567557 Title: Performance degradation of "zfs clone" Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU Justification] Creating tens of hundreds of clones can be prohibitively slow. The underlying mechanism to gather clone information is using a 16K buffer which limits performance. Also, the initial assumption is to pass in zero sized buffer to the underlying ioctl() to get an idea of the size of the buffer required to fetch information back to userspace. If we bump the initial buffer to a larger size then we reduce the need for two ioctl calls which improves performance. [Fix] Bump initial buffer size from 16K to 256K [Regression Potential] This is minimal as this is just a tweak in the initial buffer size and larger sizes are handled correctly by ZFS since they are normally used on the second ioctl() call once we have established the size of the buffer required from the first ioctl() call. Larger initial buffers just remove the need for the initial size estimation for most cases where the number of clones is less than ~5000. There is a risk that a larger buffer size could lead to a ENOMEM issue when allocating the buffer, but the size of buffer used is still trivial for modern large 64 bit servers running ZFS. [Test case] Create 4000 clones. With the fix this takes 35-40% less time than without the fix. See the example test.sh script as an example of how to create this many clones. -- I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128
[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"
This bug was fixed in the package zfs-linux - 0.6.5.9-5ubuntu4.2 --- zfs-linux (0.6.5.9-5ubuntu4.2) zesty; urgency=medium * Improve cloning performance for large numbers of clones (LP: #1567557) Bump zcmd buffer from 16K to 256K. -- Colin Ian King Thu, 10 Aug 2017 13:48:11 +0100 ** Changed in: zfs-linux (Ubuntu Zesty) Status: Fix Committed => 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/1567557 Title: Performance degradation of "zfs clone" Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU Justification] Creating tens of hundreds of clones can be prohibitively slow. The underlying mechanism to gather clone information is using a 16K buffer which limits performance. Also, the initial assumption is to pass in zero sized buffer to the underlying ioctl() to get an idea of the size of the buffer required to fetch information back to userspace. If we bump the initial buffer to a larger size then we reduce the need for two ioctl calls which improves performance. [Fix] Bump initial buffer size from 16K to 256K [Regression Potential] This is minimal as this is just a tweak in the initial buffer size and larger sizes are handled correctly by ZFS since they are normally used on the second ioctl() call once we have established the size of the buffer required from the first ioctl() call. Larger initial buffers just remove the need for the initial size estimation for most cases where the number of clones is less than ~5000. There is a risk that a larger buffer size could lead to a ENOMEM issue when allocating the buffer, but the size of buffer used is still trivial for modern large 64 bit servers running ZFS. [Test case] Create 4000 clones. With the fix this takes 35-40% less time than without the fix. See the example test.sh script as an example of how to create this many clones. -- I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 07:42:12.053] Importing image int
[Kernel-packages] [Bug 1596835] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1596835 Title: libnvpair.so.1 should be in /lib/, not /usr/lib/ Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU JUSTIFICATION XENIAL] Currently, in Ubuntu 16.04, the package libnvpair1linux puts libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which are installed in /sbin/ need this library. According to the FHS this means the required libraries should be in /lib/ in order to allow the user to install /usr/ on a separate partition that is not immediately available after boot. This turns out to be a problem indeed. On one of my systems I had /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate ext4 partition). However, the system failed to boot: it hung while mounting the ZFS partitions which failed because zpool import didn't work as it couldn't find libnvpair.so.1. $ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.6.5.6-0ubuntu9 Candidate: 0.6.5.6-0ubuntu9 Version table: *** 0.6.5.6-0ubuntu9 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu9 Candidate: 0.6.5.6-0ubuntu9 Version table: *** 0.6.5.6-0ubuntu9 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [FIX] Correctly set path by modifying the debian install files for the specific libraries to match the correct settings found in releases after Xenial. [TEST] The path /usr/lib/ should no longer be populated with zfs libraries and instead they are located after the fix in /lib as expected. [REGRESSION POTENTIAL] There could be other applications that are relying on the location of the libraries and so moving them could break these. However, they should not be using hard coded paths, so this regression is limited to badly coded applications that I am not aware of. The fix upgrade has been tested and double check with the ubuntu kernel team ZFS regression tests without issue. - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1596835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"
As per comment #24, considering the upload to be tested for zesty as well ^ ** Tags added: verification-done-zesty -- 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/1567557 Title: Performance degradation of "zfs clone" Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU Justification] Creating tens of hundreds of clones can be prohibitively slow. The underlying mechanism to gather clone information is using a 16K buffer which limits performance. Also, the initial assumption is to pass in zero sized buffer to the underlying ioctl() to get an idea of the size of the buffer required to fetch information back to userspace. If we bump the initial buffer to a larger size then we reduce the need for two ioctl calls which improves performance. [Fix] Bump initial buffer size from 16K to 256K [Regression Potential] This is minimal as this is just a tweak in the initial buffer size and larger sizes are handled correctly by ZFS since they are normally used on the second ioctl() call once we have established the size of the buffer required from the first ioctl() call. Larger initial buffers just remove the need for the initial size estimation for most cases where the number of clones is less than ~5000. There is a risk that a larger buffer size could lead to a ENOMEM issue when allocating the buffer, but the size of buffer used is still trivial for modern large 64 bit servers running ZFS. [Test case] Create 4000 clones. With the fix this takes 35-40% less time than without the fix. See the example test.sh script as an example of how to create this many clones. -- I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 07:42:12.053] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 07:42:13.351] Starting the test [Apr 3 07:42:14.793] Started 8 containers in 1.442s [Apr 3 07:42:16.495] Started 16 containers in 3.144s [Apr 3 07:42:19.881] Started 32 conta
[Kernel-packages] [Bug 1596835] Re: libnvpair.so.1 should be in /lib/, not /usr/lib/
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu18 --- zfs-linux (0.6.5.6-0ubuntu18) xenial; urgency=medium * Improve cloning performance for large numbers of clones (LP: #1567557) Bump zcmd buffer from 16K to 256K. * Correctly install libraries such as libnvpair.so.1 to /lib and not /usr/lib, this also fixes boot issues (LP: #1596835) -- Colin Ian King Fri, 11 Aug 2017 08:33:23 +0100 ** Changed in: zfs-linux (Ubuntu Xenial) Status: Fix Committed => 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/1596835 Title: libnvpair.so.1 should be in /lib/, not /usr/lib/ Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU JUSTIFICATION XENIAL] Currently, in Ubuntu 16.04, the package libnvpair1linux puts libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which are installed in /sbin/ need this library. According to the FHS this means the required libraries should be in /lib/ in order to allow the user to install /usr/ on a separate partition that is not immediately available after boot. This turns out to be a problem indeed. On one of my systems I had /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate ext4 partition). However, the system failed to boot: it hung while mounting the ZFS partitions which failed because zpool import didn't work as it couldn't find libnvpair.so.1. $ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.6.5.6-0ubuntu9 Candidate: 0.6.5.6-0ubuntu9 Version table: *** 0.6.5.6-0ubuntu9 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu9 Candidate: 0.6.5.6-0ubuntu9 Version table: *** 0.6.5.6-0ubuntu9 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [FIX] Correctly set path by modifying the debian install files for the specific libraries to match the correct settings found in releases after Xenial. [TEST] The path /usr/lib/ should no longer be populated with zfs libraries and instead they are located after the fix in /lib as expected. [REGRESSION POTENTIAL] There could be other applications that are relying on the location of the libraries and so moving them could break these. However, they should not be using hard coded paths, so this regression is limited to badly coded applications that I am not aware of. The fix upgrade has been tested and double check with the ubuntu kernel team ZFS regression tests without issue. - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1596835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714966] Re: Backport documentation and help text rework
** Changed in: ubuntu-fan (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: ubuntu-fan (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Low ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Zesty) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: ubuntu-fan (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released ** Changed in: ubuntu-fan (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714966 Title: Backport documentation and help text rework Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: After substantially enhancing all of the documentation (README and man pages) as well as the output of built-in help of fanatic, we should backport those changes to Zesty and Xenial. The changes related to this were: * fanatic: recast advanced commands as non-interactive * fanatic: fix spelling in primary help * fanatic: fix references to fanatic manual page * fanatic: Fix typo in progress output * README: Refresh documentation * fanctl.8: Refresh documentation * fanatic.8: Refresh documentation * fanatic.8: Reword advanced to non-interactive usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714966] Re: Backport documentation and help text rework
** Also affects: ubuntu-fan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714966 Title: Backport documentation and help text rework Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: After substantially enhancing all of the documentation (README and man pages) as well as the output of built-in help of fanatic, we should backport those changes to Zesty and Xenial. The changes related to this were: * fanatic: recast advanced commands as non-interactive * fanatic: fix spelling in primary help * fanatic: fix references to fanatic manual page * fanatic: Fix typo in progress output * README: Refresh documentation * fanctl.8: Refresh documentation * fanatic.8: Refresh documentation * fanatic.8: Reword advanced to non-interactive usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714969] Re: Backport remaining delta
** Changed in: ubuntu-fan (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: ubuntu-fan (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Low ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Zesty) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Released ** Changed in: ubuntu-fan (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714969 Title: Backport remaining delta Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: The remaining changes (which were not handled, yet) are: * debian/control: fix use of obsolete > operator * fanatic: fix local testing and improve docker test * fanatic: Support nc -N option * fanatic: Prevent error message without docker installed * fanatic: Supply LXD storage if needed * dep8: Add LXD auto-test * DEP8: lxd: Suppress stderr on profile list(*) All those are already present in the Zesty version of ubuntu-fan (execpt the last (*) one) and either add code to handle changes in the interfaces of nc, lxd-client, or docker (fixes testing in case those changes get backported to Xenial). Or fix/improve the built-in testing in general. Or add DEP8 tests. Normal operation is not changed. By having those changes backported to Xenial, we also would have only a single code base to maintain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714969] Re: Backport remaining delta
** Also affects: ubuntu-fan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714969 Title: Backport remaining delta Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: The remaining changes (which were not handled, yet) are: * debian/control: fix use of obsolete > operator * fanatic: fix local testing and improve docker test * fanatic: Support nc -N option * fanatic: Prevent error message without docker installed * fanatic: Supply LXD storage if needed * dep8: Add LXD auto-test * DEP8: lxd: Suppress stderr on profile list(*) All those are already present in the Zesty version of ubuntu-fan (execpt the last (*) one) and either add code to handle changes in the interfaces of nc, lxd-client, or docker (fixes testing in case those changes get backported to Xenial). Or fix/improve the built-in testing in general. Or add DEP8 tests. Normal operation is not changed. By having those changes backported to Xenial, we also would have only a single code base to maintain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714969] Re: Backport remaining delta
** Summary changed: - Backport remaining delta to Xenial + Backport remaining delta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714969 Title: Backport remaining delta Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: The remaining changes (which were not handled, yet) are: * debian/control: fix use of obsolete > operator * fanatic: fix local testing and improve docker test * fanatic: Support nc -N option * fanatic: Prevent error message without docker installed * fanatic: Supply LXD storage if needed * dep8: Add LXD auto-test * DEP8: lxd: Suppress stderr on profile list(*) All those are already present in the Zesty version of ubuntu-fan (execpt the last (*) one) and either add code to handle changes in the interfaces of nc, lxd-client, or docker (fixes testing in case those changes get backported to Xenial). Or fix/improve the built-in testing in general. Or add DEP8 tests. Normal operation is not changed. By having those changes backported to Xenial, we also would have only a single code base to maintain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714969] [NEW] Backport remaining delta
Public bug reported: The remaining changes (which were not handled, yet) are: * debian/control: fix use of obsolete > operator * fanatic: fix local testing and improve docker test * fanatic: Support nc -N option * fanatic: Prevent error message without docker installed * fanatic: Supply LXD storage if needed * dep8: Add LXD auto-test * DEP8: lxd: Suppress stderr on profile list(*) All those are already present in the Zesty version of ubuntu-fan (execpt the last (*) one) and either add code to handle changes in the interfaces of nc, lxd-client, or docker (fixes testing in case those changes get backported to Xenial). Or fix/improve the built-in testing in general. Or add DEP8 tests. Normal operation is not changed. By having those changes backported to Xenial, we also would have only a single code base to maintain. ** Affects: ubuntu-fan (Ubuntu) Importance: Low Status: Fix Released ** Affects: ubuntu-fan (Ubuntu Xenial) Importance: Low Status: In Progress ** Affects: ubuntu-fan (Ubuntu Zesty) Importance: Low Assignee: Stefan Bader (smb) Status: In Progress ** Description changed: The remaining changes (which were not handled, yet) are: - * debian/control: fix use of obsolete > operator - * fanatic: fix local testing and improve docker test - * fanatic: Support nc -N option - * fanatic: Prevent error message without docker installed - * fanatic: Supply LXD storage if needed - * dep8: Add LXD auto-test - * DEP8: lxd: Suppress stderr on profile list + * debian/control: fix use of obsolete > operator + * fanatic: fix local testing and improve docker test + * fanatic: Support nc -N option + * fanatic: Prevent error message without docker installed + * fanatic: Supply LXD storage if needed + * dep8: Add LXD auto-test + * DEP8: lxd: Suppress stderr on profile list(*) - All those are already present in the Zesty version of ubuntu-fan and - either add code to handle changes in the interfaces of nc, lxd-client, - or docker (fixes testing in case those changes get backported to - Xenial). Or fix/improve the built-in testing in general. Or add DEP8 - tests. Normal operation is not changed. By having those changes - backported to Xenial, we also would have only a single code base to - maintain. + All those are already present in the Zesty version of ubuntu-fan (execpt + the last (*) one) and either add code to handle changes in the + interfaces of nc, lxd-client, or docker (fixes testing in case those + changes get backported to Xenial). Or fix/improve the built-in testing + in general. Or add DEP8 tests. Normal operation is not changed. By + having those changes backported to Xenial, we also would have only a + single code base to maintain. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714969 Title: Backport remaining delta Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Bug description: The remaining changes (which were not handled, yet) are: * debian/control: fix use of obsolete > operator * fanatic: fix local testing and improve docker test * fanatic: Support nc -N option * fanatic: Prevent error message without docker installed * fanatic: Supply LXD storage if needed * dep8: Add LXD auto-test * DEP8: lxd: Suppress stderr on profile list(*) All those are already present in the Zesty version of ubuntu-fan (execpt the last (*) one) and either add code to handle changes in the interfaces of nc, lxd-client, or docker (fixes testing in case those changes get backported to Xenial). Or fix/improve the built-in testing in general. Or add DEP8 tests. Normal operation is not changed. By having those changes backported to Xenial, we also would have only a single code base to maintain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714966] [NEW] Backport documentation and help text rework
Public bug reported: After substantially enhancing all of the documentation (README and man pages) as well as the output of built-in help of fanatic, we should backport those changes to Zesty and Xenial. The changes related to this were: * fanatic: recast advanced commands as non-interactive * fanatic: fix spelling in primary help * fanatic: fix references to fanatic manual page * fanatic: Fix typo in progress output * README: Refresh documentation * fanctl.8: Refresh documentation * fanatic.8: Refresh documentation * fanatic.8: Reword advanced to non-interactive usage ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Assignee: Stefan Bader (smb) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1714966 Title: Backport documentation and help text rework Status in ubuntu-fan package in Ubuntu: In Progress Bug description: After substantially enhancing all of the documentation (README and man pages) as well as the output of built-in help of fanatic, we should backport those changes to Zesty and Xenial. The changes related to this were: * fanatic: recast advanced commands as non-interactive * fanatic: fix spelling in primary help * fanatic: fix references to fanatic manual page * fanatic: Fix typo in progress output * README: Refresh documentation * fanctl.8: Refresh documentation * fanatic.8: Refresh documentation * fanatic.8: Reword advanced to non-interactive usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9
** Changed in: ubuntu-power-systems 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/1686019 Title: Ubuntu 16.04.3: Qemu fails on P9 Status in The Ubuntu-power-systems project: Fix Committed Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kernel-package source package in Zesty: New Status in linux source package in Zesty: Fix Committed Bug description: Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10 tree[1], I see the following error when trying to boot a 17.04 image. 8000 DISK : "QEMU QEMU HARDDISK2.5+" Populating /pci@8002000 No NVRAM common partition, re-initializing... Scanning USB Using default console: /vdevice/vty@7100 ted RAM kernel at 40 (17995b0 bytes) C08FF Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Booting from memory... OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8) Detected machine type: 0101 command line: debug initcall_debug udbg-immortal console=/dev/hvc0 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 01bb alloc_top: 1000 alloc_top_hi : 8000 rmo_top : 1000 ram_top : 8000 instantiating rtas at 0x0daf... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x041c -> 0x041c09fd Device tree struct 0x041d -> 0x041e Quiescing Open Firmware ... Booting Linux via __start() @ 0x0040 ... I tried to add some debug options as "debug initcall_debug udbg-immortal console=/dev/hvc0" but no luck. [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10 ---uname output--- 4.10.0-19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686019/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.
** Changed in: ubuntu-power-systems Status: In Progress => 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/1706033 Title: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 == Problem Description : = While running perftool - testsuite, the perf hw breakpoint fails and it result in call traces , hence system goes for reboot . Machine details : == System : P9 , WSP , Bare metal. OS : Ubuntu 16.04.03 uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Install perf. 2. git clone perftool-testsuite. https://github.com/rfmvh/perftool-testsuite 3. Do make. 4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: kspace address execution mem:0xc035c020:x (command exitcode + output regexp parsing and call trace is seen as system goes for reboot. Call traces : === ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request for data at address 0xc135d3b8 [1602513.518553] Faulting instruction address: 0xc02869bc [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1] [1602513.518782] SMP NR_CPUS=2048 [1602513.518784] NUMA [1602513.518842] PowerNV [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci libahci [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic #24 [1602513.519524] task: c000203968c42c00 task.stack: c00020396571 [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: c0286990 [1602513.519747] REGS: c000203965713a40 TRAP: 0300 Not tainted (4.10.0-22-generic) [1602513.519876] MSR: 90009033 [1602513.519889] CR: 22002448 XER: [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 SOFTE: 1 [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 c134af00 [1602513.520058] GPR04: 4ee50300 c000203965713d20 c000203965713e00 [1602513.520058] GPR08: c135d100 c0b71020 [1602513.520058] GPR12: c0286990 c7b4f300 [1602513.520058] GPR16: [1602513.520058] GPR20: 0001 [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 4ee50300 [1602513.520058] GPR28: c134af00 c03fee038800 [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90 [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521481] Call Trace: [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 (unreliable) [1602513.521655] [c000203965713d00] [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70 [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0 [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110 [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0 [1602513.522243] Instruction dump: [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 fbc1fff0 fbe1fff8 [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378 4be66da9 6000 3d22fff0 [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]--- [1602513.522657] It goes for reboot : After booting to Ubuntu , I see series of call traces. Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0 ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for data at address 0xc13ad438 [ 3476.626422] Faulting instruction address: 0xc029a140 [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1] [ 3476.626615] SMP NR_CPUS=2048 [ 3476.626616] NUMA [ 3476.626673] PowerNV [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto ibmpowernv uio_pdrv_genirq uio autofs4 ast i2c_algo_bit ttm crc32c_vpmsum drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys
[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Just an update, setting a `i915.enable_rc6=0` kernel parameter helps and the issue is gone but, as this switches of CPU and GPU energy saving, it's rather a temporary workaround not a final solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696375] Re: cpupower suggests installation of non-existent linux-cloud-tools-generic package
** Changed in: ubuntu-power-systems 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/1696375 Title: cpupower suggests installation of non-existent linux-cloud-tools- generic package Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Problem Description === cpupower suggests installation of non-existent linux-cloud-tools-generic package Problem occurs on an IBM POWER 16.04 LTS system. Unknown whether it occurs on other architectures or later releases. When run _without package "linux-tools-$(uname -r)" installed_, cpupower will issue a complaint, suggesting to install (among others), some linux-cloud-tools-*-generic packages: $ cpupower WARNING: cpupower not found for kernel 4.4.0-75 You may need to install the following packages for this specific kernel: linux-tools-4.4.0-75-generic linux-cloud-tools-4.4.0-75-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic However, those linux-cloud-tools-*-generic package appear not to exist --at least not in the default repos. Package linux-cloud-tools-common exists, but none of the *-generic packages are available: $ apt-cache policy "linux-cloud-*" $ cat xxx linux-cloud-tools-common: Installed: (none) Candidate: 4.4.0-78.99 Version table: 4.4.0-78.99 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el Packages 4.4.0-77.98 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 4.4.0-75.96 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el Packages [...] 4.4.0-21.37 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages The cpupower command works (at least doesn't give this complaint) if the appropriate linux-tools-$(uname -r) (perhaps via linux-tools-generic) is installed, so the cloud package is maybe not needed (as least for some functionality). I think the fix is to either: a) supply the cloud packages for POWER, or b) remove the non-existent packages from cpupower's complaint message. ---uname output--- Linux fs3 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:55:30 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Firestone ---Steps to Reproduce--- Install linux-tools-common but NOT linux-tools-*-generic on a POWER 16.04 LTS system, then run cpupower. Userspace rpm: linux-tools-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685899] Re: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685899 Title: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Issue: JFS related call traces and system enters xmon when rebooted after installation Steps to reproduce: - 1 - Install Ubuntu 17.04 the system with - prepboot - /root [JFS filesystem] - swap space 2 -After installation when rebooted it gives out call traces like as below: [3.895246] Unable to handle kernel paging request for data at address 0x [3.895278] Faulting instruction address: 0xd4c5df1c [3.895284] Oops: Kernel access of bad area, sig: 11 [#1] [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA [3.895290] pSeries [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi crc32c_vpmsum [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic #16-Ubuntu [3.895304] task: c00381d3c800 task.stack: c00381fd [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: c01279d0 [3.895310] REGS: c00381fd3500 TRAP: 0300 Not tainted (4.9.0-15-generic) [3.895313] MSR: 8280b033 [ 3.895322] CR: 48008804 XER: 0001 [3.895324] CFAR: c0008a60 DAR: DSISR: 4000 SOFTE: 1 GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 GPR08: 00180e97 d4c6a608 GPR12: c01279d0 cfb90e00 GPR16: GPR20: GPR24: 1000 d4c72b38 GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs] [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs] [3.895374] Call Trace: [3.895378] [c00381fd3780] [d4c5de6c] __get_metapage+0x154/0x6f0 [jfs] (unreliable) [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs] [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs] [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 [jfs] [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240 [3.895402] [c00381fd3b00] [c032e8a8] walk_component+0x2d8/0x3f0 [3.895406] [c00381fd3b70] [c032eb94] link_path_walk+0x1d4/0x600 [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480 [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160 [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380 [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0 [3.895424] Instruction dump: [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 41820460 [3.895433] ebdd0030 41920034 e91d0008 e93f0038 811e 80e70090 39080001 [3.895441] ---[ end trace c2aa9ba09ea05eac ]--- [3.895443] [4.088560] systemd-journald[925]: Received request to flush runtime journal from PID 1 [4.362062] crypto_register_alg 'aes' = 0 [4.362112] crypto_register_alg 'cbc(aes)' = 0 [4.362150] crypto_register_alg 'ctr(aes)' = 0 [4.362191] crypto_register_alg 'xts(aes)' = 0 [4.366949] pseries_rng: Registering IBM pSeries RNG driver When I first connected to the LPAR, it was unresponsive so I restarted it from the HMC and surprisingly it came up to the login prompt and I logged into the shell. I proceeded to install the matching linux- image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the installation of the matching dbgsym wasn't as helpful as I wanted it to be. objdump, crash tool, or addr2line wouldn't give me the source line correspond to the NIP address. I then restarted the LPAR with xmon enabled and it would drop to xmon immediately after attempting to remount / and at the same location as before at __get_metapage+0x204/0x6f0 [jfs] and again with a dereference of 0x0 as the cause of the data exception 0xd649df54 <__get_metapage+508>:ld r8,8(r29) 0xd649df58 <__get_metapage+512>:ld r9,56(r31) 0xd649df5c <__get_metapage+516>:
[Kernel-packages] [Bug 1689365] Re: ibmvscsis: Do not send aborted task response
** Changed in: ubuntu-power-systems 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/1689365 Title: ibmvscsis: Do not send aborted task response Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Released Bug description: [Impact] ibmvscsis: Do not send aborted task response The driver is sending a response to the actual scsi op that was aborted by an abort task TM, while LIO is sending a response to the abort task TM. ibmvscsis_tgt does not send the response to the client until release_cmd time. The reason for this was because if we did it at queue_status time, then the client would be free to reuse the tag for that command, but we're still using the tag until the command is released at release_cmd time, so we chose to delay sending the response until then. That then caused this issue, because release_cmd is always called, even if queue_status is not. SCSI spec says that the initiator that sends the abort task TM NEVER gets a response to the aborted op and with the current code it will send a response. Thus this fix will remove that response if the CMD_T_ABORTED && !CMD_T_TAS. Another case with a small timing window is the case where if LIO sends a TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort cmd before the release_cmd for the (attemped) aborted cmd, then we need to ensure that we send the response for the (attempted) abort cmd to the client before we send the response for the TMR Abort cmd. [Test Case] As per comment #11, this requires sending manual abort signals to trigger the bug. [Fix] ibmvscsis: Fix the incorrect req_lim_delta ibmvscsis: Clear left-over abort_cmd pointers ibmvscsis: Do not send aborted task response target: Fix unknown fabric callback queue-full errors [Regression Potential] Patches are confined to ibmvscsi driver and target driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1684054] Re: [LTCTest][Opal][FW860.20] HMI recoverable errors failed to recover and system goes to dump state.
** Changed in: ubuntu-power-systems Status: In Progress => 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/1684054 Title: [LTCTest][Opal][FW860.20] HMI recoverable errors failed to recover and system goes to dump state. Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - Pridhiviraj Paidipeddi - 2017-04-17 06:08:41 == ---Problem Description--- HMI Recoverable error injection tests leads to system checkstop followed by system dump with ubuntu 17.04 os and kernel 4.10.0-19-generic ppc64le Contact Information = ppaid...@in.ibm.com ---uname output--- #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---System Hang--- System is in dumping state. after dump finishes system will IPL to OS again. ---Debugger--- A debugger is not configured == Comment: #3 - Pridhiviraj Paidipeddi - 2017-04-17 06:12:51 == # uname -a #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="17.04 (Zesty Zapus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 17.04" VERSION_ID="17.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=zesty UBUNTU_CODENAME=zesty root@p8wookie:~# == Comment: #4 - Kevin W. Rudd - 2017-04-17 11:10:22 == == Comment: #5 - MAHESH J. SALGAONKAR - 2017-04-17 13:34:03 == it looks like below commit is a culprit: === commit 2337d207288f163e10bd8d4d7eeb0c1c75046a0c Author: Nicholas Piggin Date: Fri Jan 27 14:24:33 2017 +1000 powerpc/64: CONFIG_RELOCATABLE support for hmi interrupts The branch from hmi_exception_early to hmi_exception_realmode must use a "relocatable-style" branch, because it is branching from unrelocated exception code to beyond __end_interrupts. Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman === With the above commit changes now hmi_exception_realmode() is called using bctrl which ends up messing up TOC (r2) value and further access using new r2 results into unpredictable behaviour. c0025f50 : c0025f50: 3a 01 4c 3c addis r2,r12,314 c0025f54: b0 01 42 38 addir2,r2,432 c0025f58: a6 02 08 7c mflrr0 - With above commit the hmi_exception_early() code jumps to c0025f50 (hmi_exception_realmode+0x0) which then sets up new value for r2. If we revert above commit the code jumps to c0025f58 (hmi_exception_realmode+0x8) and hmi handler works fine. After reverting above patch I don't see this issue anymore. I have rebuilt the ubuntu kernel after reverting above patch and you can find the kernel rpm at: Can you please retry your tests with above kernel and see if issue still persists. == Comment: #6 - MAHESH J. SALGAONKAR - 2017-04-17 23:02:31 == Spoke to Michael Ellerman this morning. He helped me to identify the root cause and a fix patch beow: diff --git a/arch/powerpc/kernel/exceptions-64s.S b/arch/powerpc/kernel/exceptions-64s.S index 857bf7c5b946..7cfeb8768587 100644 --- a/arch/powerpc/kernel/exceptions-64s.S +++ b/arch/powerpc/kernel/exceptions-64s.S @@ -982,7 +982,7 @@ TRAMP_REAL_BEGIN(hmi_exception_early) EXCEPTION_PROLOG_COMMON_2(PACA_EXGEN) EXCEPTION_PROLOG_COMMON_3(0xe60) addir3,r1,STACK_FRAME_OVERHEAD - BRANCH_LINK_TO_FAR(r4, hmi_exception_realmode) + BRANCH_LINK_TO_FAR(r12, hmi_exception_realmode) /* Windup the stack. */ /* Move original HSRR0 and HSRR1 into the respective regs */ ld r9,_MSR(r1) == Comment: #7 - Pridhiviraj Paidipeddi - 2017-04-18 01:52:03 == == Comment: #8 - Pridhiviraj Paidipeddi - 2017-04-18 01:53:57 == Hi Mahesh Tested all the HMI Recoverable errors on the below patched kernel, attached the corresponding executing logs. All tests are working fine. #21 SMP Mon Apr 17 12:58:30 EDT 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks == Comment: #9 - MAHESH J. SALGAONKAR - 2017-04-18 06:07:56 == (In reply to comment #8) > Hi Mahesh > Tested all the HMI Recoverable errors on the below patched kernel, attached > the corresponding executing logs. All tests are working fine. > > Linux p8wookie 4.10.0-19.bz153487-gener
[Kernel-packages] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op
** Changed in: ubuntu-power-systems Status: In Progress => 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/1689946 Title: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: State: Open by: mdate on 19 March 2017 12:33:34 On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the Bolt for T10 and am using it to do a dd with a 2M block size. Here are the commands: nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2 dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1 I get an error on the dd. root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1 dd: error writing '/dev/nvme0n1': Input/output error 1+0 records in 0+0 records out 0 bytes copied, 0.0525061 s, 0.0 kB/s dmesg shows: [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667245] Re: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667245 Title: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- After a memory DLPAR removal, kdump doesn't work: Starting Kernel crash dump capture service... [ 67.714593] kdump-tools[3850]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete Copying data : [ 2.1 %] -/usr/sbin/kdump-config: line 639: 3897 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 72.314140] kdump-tools[3850]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad address [ 73.704152] kdump-tools[3850]: * kdump-tools: failed to save vmcore in /var/crash/201702230005 [ 73.823643] kdump-tools[3850]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201702230005/dmesg.201702230005 [ 73.973813] kdump-tools[3850]: The kernel version is not supported. [ 73.974078] kdump-tools[3850]: The makedumpfile operation may be incomplete. [ 73.983506] kdump-tools[3850]: The dmesg log is saved to /var/crash/201702230005/dmesg.201702230005. [ 73.983752] kdump-tools[3850]: makedumpfile Completed. [ 73.983998] kdump-tools[3850]: * kdump-tools: saved dmesg content in /var/crash/201702230005 [ 74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600 [ 74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No such file or directory [ 74.233782] kdump-tools[3850]: Rebooting. [ 86.629777] reboot: Restarting system The kdump service should be restarted after the memory DLPAR operation. C ---uname output--- Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. do a memory DLPAR removal operation 3. trigger kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1667245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678745 Title: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Lata Kuntal - 2017-03-30 09:44:23 == Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running few hours of regression test it dropped at xmon. Console logs : root@guskvm:~# virsh console gusg8 --force Connected to domain gusg8 Escape character is ^] 1:mon> r R00 = d288edf4 R16 = 024200ca R01 = c000378cb1f0 R17 = R02 = d2936080 R18 = 0020 R03 = 0001 R19 = c002734d1800 R04 = c000378cb190 R20 = R05 = R21 = R06 = 3c00d03fe056 R22 = c0027e26ccf0 R07 = R23 = R08 = c48492d0 R24 = R09 = 3c00d03fe056 R25 = R10 = 3c00d03fe062 R26 = 00024df4cd49 R11 = d28fa360 R27 = R12 = R28 = d28ac7b0 R13 = cfb80900 R29 = c4849000 R14 = R30 = R15 = c137ad08 R31 = pc = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs] cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440 lr = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs] msr = 80010280b033 cr = 82428424 ctr = c05e4950 xer = 2000 trap = 300 dar = 3c00d03fe062 dsisr = 4000 1:mon> t [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs] [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs] [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120 [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0 [c000378cb430] c0276db8 shrink_node+0x158/0x3f0 [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460 [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280 [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30 [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360 [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0 [c000378cb920] c02a0770 do_wp_page+0x210/0xb20 [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0 [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0 [c000378cbb10] c0008948 handle_page_fault+0x10/0x30 --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0 [c000378cbe30] c0009844 ret_from_fork+0x4/0x54 --- Exception: c00 (System Call) at 3fffa2b5bf44 1:mon> d || 1:mon> c cpus stopped: 0x0-0x3 1:mon> Kernel host build = root@guskvm:~# uname -r 4.10.0-13-generic root@guskvm:~# == Comment: #1 - Luciano Chavez - 2017-03-30 10:42:15 == At first glance, based on the following assembly from around the failure point: d288edd4 38c1 li r6,1 d288edd8 7f8802a6 mflrr28 d288eddc 78a70020 clrldi r7,r5,32 d288ede0 7c7d1b78 mr r29,r3 d288ede4 7c852378 mr r5,r4 d288ede8 386302c8 addir3,r3,712 d288edec 38810020 addir4,r1,32 d288edf0 4806b571 bl d28fa360# exit_xfs_fs+0x180c/0xfd44 [xfs] d288edf4 e8410018 ld r2,24(r1) d288edf8 2f83 cmpwi cr7,r3,0 d288edfc 409d0104 ble cr7,d288ef00# xfs_perag_get_tag+0x160/0x170 [xfs] d288ee00 7c0004ac sync d288ee04 e9210020 ld r9,32(r1) d288ee08 3949000c addir10,r9,12 d288ee0c 7fc05028 lwarx r30,0,r10 d288ee10 33de0001 addic r30,r30,1 d288ee14 7fc0512d stwcx. r30,0,r10 I believe the crash in fs_perag_get_tag() is after we come back from the radix_tree_gang_lookup_tag() call and are attempting the atomic_inc_return() and struct xfs_perag*pag is R09 = 3c00d03fe056 which is invalid. 85 rcu_read_lock(); 86 found = radix_tree_gang_lookup_tag(&mp->m_perag_tre
[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1711358 Title: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver Status in linux package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Test Case 1. Boot artful desktop 20170817 under qemu with qxl 2. Wait until ubiquity-dm is displayed Expected result It boots Actual result It hangs on the splash screen and the dots below the Ubuntu logo are not blinking. If the option 'splash' is removed from the boot command line it boots successfully. It also boots successfully with -vga std but in this case the splash screen is in text mode not graphical unlike with the qxl driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic
John: Sorry, I forgot to mention, I installed the drivers from the "Additional Drivers" menu (I run Gnome), and also from "the" PPA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697556 Title: Computer freezes after login - 4.10.0-22-generic Status in linux package in Ubuntu: Confirmed Bug description: I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days ago. Login worked fine too. A couple of days later I installed the suggested kernel update "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer freezes right after login (i.e. after pressing enter, the background image with the mouse is shown, no responses to any key strokes). Syslog excerpt: Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672] Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf intel_lpss_pci intel_pch_thermal Jun 12 22:12:48 computername kernel: [ 47.603422] hci_uart btbcm btqca btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid pinctrl_sunrisepoint video wmi pinctrl_intel fjes Jun 12 22:12:48 computername kernel: [ 47.603453] CPU: 1 PID: 1672 Comm: Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu Jun 12 22:12:48 computername kernel: [ 47.603453] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017 Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not observed with 4.10.0-21-generic. As I was not able to login to my computer I am writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore the information attached through the "ubuntu-bug linux" command here, are referring to the kernel that is actually working. I decided to nonetheless include that information as it might contain other kernel unrelated information that would help you troubleshooting. Please see attached file "syslog-4.10.0-22-generic-freeze-after- login.log" for the full syslog. 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 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hkuehn 1796 F pulseaudio CurrentDesktop: GNOME Date: Mon Jun 12 23:17:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (13 days ago) InstallationMedia: Ubuntu-GNOME 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 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.mo
[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic
John: I tried 4.10.0-33-generic, I tried 32-generic, and several versions before. I'm running the latest firmware from Dell, 1.3.4 I believe, and had something older before that. Almost every time I boot with nvidia installed it freezes at the FDE prompt, and I can't enter my password. If I don't have nvidia installed, it freezes when I try to login. I have tried various combinations of black/whitelisting modules, nvidia installed and uninstalled and nothing seems to work. One think that probably contributed was that at one point I had XWayland installed, I went back and installed ubuntu-desktop but there is probably some holdout somewhere in the configs that's breaking it. Since it freezes before the FDE pass, I can't get any useful logs and can't switch TTYs or get out of the plymouth splash to see what's behind it. It's also worth mentioning that if I boot 4.10 into recovery mode and drop to a root shell it boots fine, which is why I'm certain it's related to video drivers (it's also one of the first things loaded in the grub config I noticed. I suspect a fresh installed might help me get around this, but it's a work machine and I don't currently have the time to set up from scratch, also, that doesn't help pinpoint the issue. For the time being I'm stuck on 4.8 because it boots and I can carry on working. I run only in intel mode, I have no requirement in my day to day work to run nvidia and the battery benefits of being on intel are more beneficial to any graphical/performance benefits. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697556 Title: Computer freezes after login - 4.10.0-22-generic Status in linux package in Ubuntu: Confirmed Bug description: I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days ago. Login worked fine too. A couple of days later I installed the suggested kernel update "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer freezes right after login (i.e. after pressing enter, the background image with the mouse is shown, no responses to any key strokes). Syslog excerpt: Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672] Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf intel_lpss_pci intel_pch_thermal Jun 12 22:12:48 computername kernel: [ 47.603422] hci_uart btbcm btqca btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid pinctrl_sunrisepoint video wmi pinctrl_intel fjes Jun 12 22:12:48 computername kernel: [ 47.603453] CPU: 1 PID: 1672 Comm: Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu Jun 12 22:12:48 computername kernel: [ 47.603453] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017 Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not observed with 4.10.0-21-generic. As I was not able to login to my computer I am writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore the information attached through the "ubuntu-bug linux" command here, are referring to the kernel that is actually working. I decided to nonetheless include that information as it might contain other kernel unrelated information that would help you troubleshooting. Please see attached file "syslog-4.10.0-22-generic-freeze-after- login.log" for the full syslog. 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 ApportV
[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests
You can add/remove kernels to the guest by mounting them like via qemu-nbd. To properly install boot it directly in kvm and then run dpkg. That way I tested the mainline kernel above and the same way I switched back to [1]. With that I got correctly the older kernel: autopkgtest [13:48:11]: testbed running kernel: Linux 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3 15:13:04 UTC 2017 With that 3/3 runs with OVS 2.8 are good, so I think we can conclude this is a regression due to the kernel 4.12 update. [1]: https://launchpad.net/ubuntu/+source/linux/4.11.0-13.19/+build/13193104 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712831 Title: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests Status in linux package in Ubuntu: Confirmed Bug description: Hi, this seems to me to be a kernel crash of some sorts. Somewhat in the spirit of older bugs: - bug 1630940 - bug 1630578 Xnox asked me to look into a hang on openvswitch dep8 tests. What I found initially was in the log just "ERROR: Removing temporary files on testbed timed out" That message brought me to the two bugs above. But in there I read that this was the infra running dep8 crashing. So for a better bug report I tried to reproduce locally and that actually seems to work very reliable. To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing But with that running you can attach to the console and monitor of that guest. For example: $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0 That gave me a crash on the hang which kind of matches the older bugs, here the console: [ 54.256253] BUG: unable to handle kernel NULL pointer dereference at (null) [ 54.257156] IP: add_grec+0x28/0x440 [ 54.257553] *pdpt = 1a869001 *pde = [ 54.257555] [ 54.258338] Oops: [#1] SMP [ 54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net floppy pata_acpi [ 54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.12.0-11-generic #12-Ubuntu [ 54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 54.263610] task: c7b622c0 task.stack: c7b5a000 [ 54.264039] EIP: add_grec+0x28/0x440 [ 54.264378] EFLAGS: 00010202 CPU: 0 [ 54.264711] EAX: EBX: dd062540 ECX: 0006 EDX: dd062540 [ 54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0 [ 54.265793] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.266297] CR0: 80050033 CR2: CR3: 1e930d80 CR4: 06f0 [ 54.266885] Call Trace: [ 54.267120] [ 54.267349] mld_ifc_timer_expire+0xfe/0x250 [ 54.267754] ? mld_dad_timer_expire+0x50/0x50 [ 54.268173] call_timer_fn+0x30/0x120 [ 54.268524] ? mld_dad_timer_expire+0x50/0x50 [ 54.268942] ? mld_dad_timer_expire+0x50/0x50 [ 54.269364] run_timer_softirq+0x3c5/0x420 [ 54.269760] ? __softirqentry_text_start+0x8/0x8 [ 54.270198] __do_softirq+0xa9/0x245 [ 54.270539] ? __softirqentry_text_start+0x8/0x8 [ 54.270976] do_softirq_own_stack+0x24/0x30 [ 54.271373] [ 54.271611] irq_exit+0xad/0xb0 [ 54.271913] smp_apic_timer_interrupt+0x38/0x50 [ 54.272344] apic_timer_interrupt+0x39/0x40 [ 54.272745] EIP: native_safe_halt+0x5/0x10 [ 54.273139] EFLAGS: 0246 CPU: 0 [ 54.273624] EAX: EBX: ECX: 0001 EDX: [ 54.274000] ESI: EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10 [ 54.274361] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.274687] default_idle+0x1c/0xf0 [ 54.274896] arch_cpu_idle+0xe/0x10 [ 54.275286] default_idle_call+0x1e/0x30 [ 54.275787] do_idle+0x145/0x1c0 [ 54.276092] cpu_startup_entry+0x65/0x70 [ 54.276441] rest_init+0x62/0x70 [ 54.276718] start_kernel+0x3be/0x3d7 [ 54.276974] i386_start_kernel+0x9d/0xa1 [ 54.277260] startup_32_smp+0x16b/0x16d [ 54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b [ 54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0 [ 54.279829] CR2: [
[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests
There could be two potential changes that caused this regression, looking at [1]: It either is the newer OVS 2.8 or the Kernel 4.12. There are two good tests with OVS-2.8 in a row. 2017-08-10 16:37:12 UTC 2017-08-14 11:20:32 UTC Given the current rate of success (5/24) it is rather unlikely that this case had the issue present. Then on "Published on 2017-08-16" we got kernel 4.12 [2] and since then the issues occur. So no hard guarantee, but all data points to 4.12 to be the regressing change. [1]: http://autopkgtest.ubuntu.com/packages/openvswitch/artful/i386 [2]: https://launchpad.net/ubuntu/+source/linux/4.12.0-11.12 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712831 Title: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests Status in linux package in Ubuntu: Confirmed Bug description: Hi, this seems to me to be a kernel crash of some sorts. Somewhat in the spirit of older bugs: - bug 1630940 - bug 1630578 Xnox asked me to look into a hang on openvswitch dep8 tests. What I found initially was in the log just "ERROR: Removing temporary files on testbed timed out" That message brought me to the two bugs above. But in there I read that this was the infra running dep8 crashing. So for a better bug report I tried to reproduce locally and that actually seems to work very reliable. To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing But with that running you can attach to the console and monitor of that guest. For example: $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0 That gave me a crash on the hang which kind of matches the older bugs, here the console: [ 54.256253] BUG: unable to handle kernel NULL pointer dereference at (null) [ 54.257156] IP: add_grec+0x28/0x440 [ 54.257553] *pdpt = 1a869001 *pde = [ 54.257555] [ 54.258338] Oops: [#1] SMP [ 54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net floppy pata_acpi [ 54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.12.0-11-generic #12-Ubuntu [ 54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 54.263610] task: c7b622c0 task.stack: c7b5a000 [ 54.264039] EIP: add_grec+0x28/0x440 [ 54.264378] EFLAGS: 00010202 CPU: 0 [ 54.264711] EAX: EBX: dd062540 ECX: 0006 EDX: dd062540 [ 54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0 [ 54.265793] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.266297] CR0: 80050033 CR2: CR3: 1e930d80 CR4: 06f0 [ 54.266885] Call Trace: [ 54.267120] [ 54.267349] mld_ifc_timer_expire+0xfe/0x250 [ 54.267754] ? mld_dad_timer_expire+0x50/0x50 [ 54.268173] call_timer_fn+0x30/0x120 [ 54.268524] ? mld_dad_timer_expire+0x50/0x50 [ 54.268942] ? mld_dad_timer_expire+0x50/0x50 [ 54.269364] run_timer_softirq+0x3c5/0x420 [ 54.269760] ? __softirqentry_text_start+0x8/0x8 [ 54.270198] __do_softirq+0xa9/0x245 [ 54.270539] ? __softirqentry_text_start+0x8/0x8 [ 54.270976] do_softirq_own_stack+0x24/0x30 [ 54.271373] [ 54.271611] irq_exit+0xad/0xb0 [ 54.271913] smp_apic_timer_interrupt+0x38/0x50 [ 54.272344] apic_timer_interrupt+0x39/0x40 [ 54.272745] EIP: native_safe_halt+0x5/0x10 [ 54.273139] EFLAGS: 0246 CPU: 0 [ 54.273624] EAX: EBX: ECX: 0001 EDX: [ 54.274000] ESI: EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10 [ 54.274361] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.274687] default_idle+0x1c/0xf0 [ 54.274896] arch_cpu_idle+0xe/0x10 [ 54.275286] default_idle_call+0x1e/0x30 [ 54.275787] do_idle+0x145/0x1c0 [ 54.276092] cpu_startup_entry+0x65/0x70 [ 54.276441] rest_init+0x62/0x70 [ 54.276718] start_kernel+0x3be/0x3d7 [ 54.276974] i386_start_kernel+0x9d/0xa1 [ 54.277260] startup_32_smp+0x16b/0x16d [ 54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b [ 54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef
[Kernel-packages] [Bug 1712724] Comment bridged from LTC Bugzilla
--- Comment From geral...@de.ibm.com 2017-09-04 07:03 EDT--- This looks like the bug that was fixed by Martin just recently: commit 8ab867cb0806a8e195de161fd8883a0578d1d050 Author: Martin Schwidefsky Date: Thu Aug 31 13:18:22 2017 +0200 s390/mm: fix BUG_ON in crst_table_upgrade A 31-bit compat process can force a BUG_ON in crst_table_upgrade with specific, invalid mmap calls, e.g. mmap((void*) 0x7fff8000, 0x1, 3, 32, -1, 0) The arch_get_unmapped_area[_topdown] functions miss an if condition in the decision to do a page table upgrade. Fixes: 9b11c7912d00 ("s390/mm: simplify arch_get_unmapped_area[_topdown]") Cc: # v4.12+ Signed-off-by: Martin Schwidefsky -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom,
[Kernel-packages] [Bug 1712724] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2017-09-04 06:54 EDT--- FWIW, the oops message indicates that the task_size_overrun testcase triggered the kernel 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/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (proba
[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
I'm on kernel 4.13 and got this error message as well. The external monitor connected to laptop (Razer Blade Stealth) flickers a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712724] UdevDb.txt
Default Comment by Bridge ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1712724/+attachment/4944060/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To
[Kernel-packages] [Bug 1712724] WifiSyslog.txt
Default Comment by Bridge ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1712724/+attachment/4944061/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh inst
[Kernel-packages] [Bug 1712724] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2017-09-04 06:26 EDT--- Some questions: - this Ubuntu instance was running under KVM, correct? - I assume that the testcase also fails when running under z/VM or in LPAR? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: l
[Kernel-packages] [Bug 1714930] Re: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1714930 Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-signed package in Ubuntu: New Bug description: I cannot install any new package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Sep 4 13:20:35 2017 DpkgHistoryLog: Start-Date: 2017-09-04 13:20:08 Commandline: aptdaemon role='role-install-packages' sender=':1.77' Install: libhsqldb1.8.0-java:amd64 (1.8.0.10+dfsg-6, automatic), libreoffice-java-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-sdbc-firebird:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-sdbc-hsqldb:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base-drivers:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic) DuplicateSignature: package:linux-signed-image-4.4.0-66-generic:4.4.0-66.87 Setting up linux-signed-image-4.4.0-64-generic (4.4.0-64.85) ... cp: cannot stat '/boot/vmlinuz-4.4.0-64-generic': No such file or directory dpkg: error processing package linux-signed-image-4.4.0-64-generic (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-07 (454 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-signed Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1714930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714930] [NEW] package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I cannot install any new package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Sep 4 13:20:35 2017 DpkgHistoryLog: Start-Date: 2017-09-04 13:20:08 Commandline: aptdaemon role='role-install-packages' sender=':1.77' Install: libhsqldb1.8.0-java:amd64 (1.8.0.10+dfsg-6, automatic), libreoffice-java-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-sdbc-firebird:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-sdbc-hsqldb:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base-drivers:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic) DuplicateSignature: package:linux-signed-image-4.4.0-66-generic:4.4.0-66.87 Setting up linux-signed-image-4.4.0-64-generic (4.4.0-64.85) ... cp: cannot stat '/boot/vmlinuz-4.4.0-64-generic': No such file or directory dpkg: error processing package linux-signed-image-4.4.0-64-generic (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-07 (454 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-signed Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1714930 Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-signed package in Ubuntu: New Bug description: I cannot install any new package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Sep 4 13:20:35 2017 DpkgHistoryLog: Start-Date: 2017-09-04 13:20:08 Commandline: aptdaemon role='role-install-packages' sender=':1.77' Install: libhsqldb1.8.0-java:amd64 (1.8.0.10+dfsg-6, automatic), libreoffice-java-common:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2), libreoffice-sdbc-firebird:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-sdbc-hsqldb:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic), libreoffice-base-drivers:amd64 (1:5.1.6~rc2-0ubuntu1~xenial2, automatic) DuplicateSignature: package:linux-signed-image-4.4.0-66-generic:4.4.0-66.87 Setting up linux-signed-image-4.4.0-64-generic (4.4.0-64.85) ... cp: cannot stat '/boot/vmlinuz-4.4.0-64-generic': No such file or directory dpkg: error processing package linux-signed-image-4.4.0-64-generic (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-07 (454 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-signed Title: package linux-signed-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1714930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug
I'm able to reproduce the issue locally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs] [ 5281.179640] [<03ff805ec668>] xfsaild+0x170/0x798 [xfs] [ 5281.179643] [<0018335a>] kthread+0x10a/0x110 [ 5281.179645
[Kernel-packages] [Bug 1712724] Re: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c
--- Comment From heinz-werner_se...@de.ibm.com 2017-09-04 05:16 EDT--- See Problem descripton from Canonical. ** Tags added: architecture-s39064 bugnameltc-158248 severity-high targetmilestone-inin1710 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712724 Title: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c Status in linux package in Ubuntu: Triaged Bug description: [ 543.516708] kernel BUG at /build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84! [ 543.516783] illegal operation: 0001 ilc:1 [#1] SMP [ 543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi [ 543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P O 4.12.0-12-generic #13-Ubuntu [ 543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux) [ 543.516830] task: 0cdb9e00 task.stack: 099e8000 [ 543.516831] Krnl PSW : 0704d0018000 001274ec (crst_table_upgrade+0x124/0x130) [ 543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 543.516842] Krnl GPRS: 0001 0400 243d7800 0020 [ 543.516843]1000 0032 [ 543.516844]8000 0020 1000 [ 543.516845]0020 243d7800 001239f6 099ebbe0 [ 543.516853] Krnl Code: 001274de: c0e5002446c1 brasl %r14,5b0260 [ 543.516853]001274e4: a7f4ffb8 brc 15,127454 [ 543.516853] #001274e8: a7f40001 brc 15,1274ea [ 543.516853] >001274ec: a728fff4 lhi %r2,-12 [ 543.516853]001274f0: a7f4ffee brc 15,1274cc [ 543.516853]001274f4: 0707 bcr 0,%r7 [ 543.516853]001274f6: 0707 bcr 0,%r7 [ 543.516853]001274f8: c004 brcl0,1274f8 [ 543.516862] Call Trace: [ 543.516864] ([<085d8578>] 0x85d8578) [ 543.516868] [<002f529a>] get_unmapped_area+0x72/0x120 [ 543.516870] [<002f931a>] do_mmap+0xfa/0x3e0 [ 543.516873] [<002d6292>] vm_mmap_pgoff+0xca/0x120 [ 543.516874] [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 [ 543.516875] [<002f6b72>] SyS_old_mmap+0x7a/0xa8 [ 543.516880] [<00864c1c>] system_call+0xc4/0x27c [ 543.516881] Last Breaking-Event-Address: [ 543.516882] [<001274e8>] crst_table_upgrade+0x120/0x130 [ 543.516883] [ 543.516883] ---[ end trace 036f94bf79a83905 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.12.0-12-generic 4.12.0-12.13 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.6-0ubuntu6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 24 05:01:08 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.12.0-12-generic N/A linux-backports-modules-4.12.0-12-generic N/A linux-firmware 1.167 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux
[Kernel-packages] [Bug 1670634] cpuplugd.conf
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2017-09-04 04:51 EDT--- ** Attachment added: "cpuplugd.conf" https://bugs.launchpad.net/bugs/1670634/+attachment/4943992/+files/cpuplugd.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff
[Kernel-packages] [Bug 1670634] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2017-09-04 04:52 EDT--- no specific cpu (un)plug tests where executed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670634 Title: blk-mq: possible deadlock on CPU hot(un)plug Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Carsten Jacobi - 2017-03-07 03:35:31 == I'm evaluating Ubuntu-Xenial on z for development purposes, the test system is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all pathes are configured). The system hangs regularly when I make packages with "pdebuild" using the pbuilder packaging suit. The local Linux development team helped me out with a pre-analysis that I can post here (thanks a lot for that): With the default settings and under a certain workload, blk_mq seems to get into a presumed "deadlock". Possibly this happens on CPU hot(un)plug. After the I/O stalled, a dump was pulled manually. The following information is from the crash dump pre-analysis. $ zgetdump -i dump.0 General dump info: Dump format: elf Version: 1 UTS node name..: mclint UTS kernel release.: 4.4.0-65-generic UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 System arch: s390x (64 bit) CPU count (online).: 2 Dump memory range..: 8192 MB Memory map: - 0001b831afff (7043 MB) 0001b831b000 - 0001 (1149 MB) Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1. KERNEL: vmlinux.full DUMPFILE: dump.0 CPUS: 2 DATE: Fri Mar 3 14:31:07 2017 UPTIME: 02:11:20 LOAD AVERAGE: 13.00, 12.92, 11.37 TASKS: 411 NODENAME: mclint RELEASE: 4.4.0-65-generic VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 MACHINE: s390x (unknown Mhz) MEMORY: 7.8 GB PANIC: "" PID: 0 COMMAND: "swapper/0" TASK: bad528 (1 of 2) [THREAD_INFO: b78000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) INFO: no panic task found crash> dev -d MAJOR GENDISKNAME REQUEST_QUEUE TOTAL ASYNC SYNC DRV ... 8 1e1d6d800 sda1e1d51210 0 23151 4294944145 N/A(MQ) 8 1e4e06800 sdc2081b180 23148 4294944148 N/A(MQ) 8 1f07800sdb20c75680 23195 4294944101 N/A(MQ) 8 1e4e06000 sdd1e4e31210 0 23099 4294944197 N/A(MQ) 252 1e1d6c800 dm-0 1e1d51b18 9 1 8 N/A(MQ) ... So both dm-mpath and sd have requests pending in their block multiqueue. The large numbers of sd look strange and seem to be the unsigned formatting of the values shown for async multiplied by -1. [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49) [0.798262] setup: Linux is running natively in 64-bit mode [0.798290] setup: Max memory size: 8192MB [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel (System RAM: 7996MB) [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0 [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 seconds. [ 5281.179437] Not tainted 4.4.0-65-generic #86-Ubuntu [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 5281.179440] xfsaild/dm-11 D 007bcf52 0 1604 2 0x [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 0001e6f9b9d8 0001e15795f0 0001e6f9b988 00ce8c00 0001ea805c70 0001ea805c00 00ba5ed0 0001e931c1d0 0001e1579b20 0001ea805c00 0001e15795f0 0001ea805c00 007d3978 007bc9f8 0001e6f9b9d8 0001e6f9ba40 [ 5281.179454] Call Trace: [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810) [ 5281.179462] [<007bcf52>] schedule+0x4a/0xb0 [ 5281.179465] [<007c02aa>] schedule_timeout+0x232/0x2a8 [ 5281.179466] [<007bde50>] wait_for_common+0x110/0x1c8 [ 5281.179472] [<0017b602>] flush_work+0x42/0x58 [ 5281.179564] [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs] [ 5281.179589] [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs] [ 5281.179615] [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs] [ 5281.179640] [<03ff805ec668>] xfsaild+0x17
[Kernel-packages] [Bug 1714190] Re: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM
This test has passed on Zesty zVM and zKVM. I will mark this one as fix- released. Thanks! ** Changed in: linux (Ubuntu) Status: In Progress => 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/1714190 Title: ubuntu_sysdig_smoke_test stuck on Zesty s390x zKVM / zVM Status in linux package in Ubuntu: Fix Released Bug description: From the test log, it looks like this test get stuck on s390x zVM and zKVM (kernel03, s2lp6g003) for a couple hours with zesty kernel. 01:14:28 DEBUG| Running '/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh' 01:14:28 DEBUG| [stdout] == sysdig smoke test to trace dd, cat, read and writes == 01:14:28 DEBUG| [stdout] Try 1 of 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714571] Re: [P9, POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714571 Title: [P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 == ---Problem Description--- Problem description : = Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is because two raw point to the same name. [ {, "EventCode": "0x20036", "EventName": "PM_BR_2PATH", "BriefDescription": "Branches that are not strongly biased", "PublicDescription": "" }, {, "EventCode": "0x40036", "EventName": "PM_BR_2PATH", "BriefDescription": "Branches that are not strongly biased", "PublicDescription": "" }, Ex : === [root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1 Performance counter stats for 'sleep 1': 30,163 pm_br_2path pm_br_2path (0.00%) 1.002046416 seconds time elapsed [root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1 Performance counter stats for 'sleep 1': 9,217 pm_ld_miss_l1 pm_ld_miss_l1 (0.00%) 1.001956110 seconds time elapsed ---Steps to Reproduce--- Steps to reproduce : 1. Install perf (linux-tools) 2. Run perf stat -e pm_ld_miss_l1 sleep 1 perf stat -e pm_br_2path sleep 1 == Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 == The fix for this bug was pulled into Arnaldo's tree: https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696049] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2017-09-04 02:40 EDT--- (In reply to comment #21) > Can you test the following kernels and report back? We are looking for the > last kernel version that has the bug and the first that does not: > > v4.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/ > v4.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4/ > v4.11-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8/ Issue is observed on all the above kernels. But not on http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.12/. Thanks, Harish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696049 Title: xfstest sanity checks on seek operations fails Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Harish Sriram Issue: -- xfstest fails with sanity checks on seek operations # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/285 or ./check tests/generic/436 The test 285 fails with following ... ... 07. Test file with unwritten extents, only have dirty pages 07.01 SEEK_HOLE expected 0 or 45056, got 0. succ 07.02 SEEK_HOLE expected 1 or 45056, got 1. succ 07.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 07.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08. Test file with unwritten extents, only have unwritten pages 08.01 SEEK_HOLE expected 0 or 45056, got 0. succ 08.02 SEEK_HOLE expected 1 or 45056, got 1. succ 08.03 SEEK_DATA expected 40960 or 40960, got -1. FAIL 08.04 SEEK_DATA expected 40960 or 40960, got -1. FAIL The test 436 fails with ... ... 14. Test file with unwritten extents, small hole after pagevec dirty pages 14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016. FAIL 14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ 14.04 SEEK_DATA expected 0 or 0, got 0. succ 14.05 SEEK_DATA expected 1 or 1, got 1. succ 14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ seek sanity check failed! Full log is attached. == Comment: #6 - Harish Sriram commit 5375023ae1266553a7baa0845e82917d8803f48c Author: Jan Kara Date: Thu May 18 16:36:22 2017 -0700 xfs: Fix missed holes in SEEK_HOLE implementation XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k" -c "seek -h 0" file wrote 57344/57344 bytes at offset 0 56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec) wrote 8192/8192 bytes at offset 131072 8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec) Whence Result HOLE139264 Where we can see that hole at offset 56k was just ignored by SEEK_HOLE implementation. The bug is in xfs_find_get_desired_pgoff() which does not properly detect the case when pages are not contiguous. Fix the problem by properly detecting when found page has larger offset than expected. CC: sta...@vger.kernel.org Fixes: d126d43f631f996daeee5006714fed914be32368 Signed-off-by: Jan Kara Reviewed-by: Brian Foster Reviewed-by: Darrick J. Wong Signed-off-by: Darrick J. Wong The above commit fixes the generic/436 test, but generic/285 still FAILS. The generic/285 failure is reproducible on most P8/P9 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp