[Kernel-packages] [Bug 1840454] Re: kernel 5.2 disallows thermald's direct MSR writes
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1840454 Title: kernel 5.2 disallows thermald's direct MSR writes Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: thermald/kernel are spamming dmesg now because MSR write is disallowed. jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | wc -l 8688 jak@jak-t480s:~:master$ journalctl -b --since=today | grep msr | tail Aug 16 14:48:57 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:48:57 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:05 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:05 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:13 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:13 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:49:21 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr Aug 16 14:49:21 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s kernel: msr: Direct access to MSR 1a2 Aug 16 14:50:03 jak-t480s thermald[11327]: [WARN]sysfs write failed /dev/cpu/0/msr --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5499 F pulseaudio /dev/snd/controlC1: jak5499 F pulseaudio /dev/snd/controlC0: jak5499 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (520 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: thermald 1.9.0-1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-10-generic root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 Tags: eoan third-party-packages Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-20 (269 days ago) UserGroups: adm cdrom dip fax input kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 04/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 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: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET54W(1.31):bd04/22/2019:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: Confirmed Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlastimil 2458 F pulseaudio /dev/snd/controlC1: vlastimil 2458 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-06-16 (430 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180531 MachineType: Dell Inc. Inspiron 7577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro ipv6.disable=1 quiet splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0J8HMF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd04/19/2019:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0J8HMF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794876] Re: Touchpad doesn't work out-of-the-box in Ubuntu 18.04.1 with ThinkPad X1 carbon
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794876 Title: Touchpad doesn't work out-of-the-box in Ubuntu 18.04.1 with ThinkPad X1 carbon Status in linux package in Ubuntu: Confirmed Bug description: The touchpad doesn't work after installing Ubuntu 18.04.1 on a new Lenovo ThinkPad X1 Carbon laptop. I see log messages like these repeatedly: ``` Sep 27 15:41:17 jik-x1 kernel: [3.824013] psmouse serio2: Failed to reset mouse on synaptics-pt/serio0 Sep 27 15:41:17 jik-x1 kernel: [9.388812] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0 Sep 27 15:41:30 jik-x1 kernel: [ 33.124787] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Sep 27 15:41:30 jik-x1 kernel: [ 33.126159] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Sep 27 15:41:30 jik-x1 kernel: [ 33.127437] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Sep 27 15:41:30 jik-x1 kernel: [ 33.132428] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Sep 27 15:41:30 jik-x1 kernel: [ 33.133608] psmouse serio1: TouchPad at isa0060/serio1/input0 lost sync at byte 1 Sep 27 15:41:30 jik-x1 kernel: [ 33.133613] psmouse serio1: issuing reconnect request ``` I also saw this on boot: ``` Sep 27 14:00:29 jik-x1 kernel: [3.405390] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. ``` The touchpad works for a second or two after it is reset and then stops working again. There are other bugs about this (e.g., https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723986) but they claim the issue is fixed. To fix this I had to: 1. Remove `blacklist i2c_i801` from `/etc/modprobe.d/blacklist.conf`. 2. Update my initramfs after doing so. 3. Add `psmouse.synaptics_intertouch=1` to `GRUB_CMDLINE_LINUX_DEFAULT` in `/etc/default/grub`. 4. Update my grub configuration after doing so. 5. Reboot. Neither of these fixes by itself was sufficient. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jik4438 F pulseaudio /dev/snd/controlC1: jik4438 F pulseaudio /dev/snd/controlC0: jik4438 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 17:06:49 2018 HibernationDevice: RESUME=UUID=809b24c2-f7bc-493e-97dc-02bd6293d3bc InstallationDate: Installed on 2018-09-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817070] Re: Thunderbolt display not detected
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817070 Title: Thunderbolt display not detected Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell XPS 13 (9370) connected to a Caldigit TS3 Plus thunderbolt dock. On this dock I have two monitors connected. One is connected to the display port of the dock, the second one is connected to an USB-C Thunderbolt port using an USB-C to mini DP adapter. The second monitor is only detected, when I _first_ plug in the adapter and _then_ plug in the the cable to the adapter. This also only works when the system has booted _and_ I am logged in. I already disabled thunderbolt security completely in UEFI. Once the monitor has been detected it is also working during boot, when I restart the system. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: max1628 F...m pulseaudio /dev/snd/controlC0: max1628 F pulseaudio /dev/snd/controlC1: max1628 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=e6ab437d-a79f-412f-bed4-1a80bbde0736 InstallationDate: Installed on 2019-01-05 (47 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Dell Inc. XPS 13 9370 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/mint--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 09DKKT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn09DKKT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
Brian, aws, aws-hwe and aws-edge are derivative kernels of the generic kernels. as such they automatically pick up all fixes that get applied to the generic kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: New Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: New Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a9688171a6] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe8160e1830] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55a968801329] (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log"
[Kernel-packages] [Bug 1839124] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839124 Title: BT advertising packet wakes up the system from S3 and suspend-to-idle Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007). Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected. By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue. The advertising packet could be none connectable undirected or connectable undirected. And the BT4 devices we found can reproduce this issue are 1. Microsoft Surface 1678 2. Logitech K375s 3. Microsoft Designer Mouse --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1539 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0FN010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839856] Re: Screen resolution on external monitor won't go above 2560 x 1080
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839856 Title: Screen resolution on external monitor won't go above 2560 x 1080 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: I have an external monitor capable of 3440 x 1440. I am using a Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution of the monitor to 3440 x 1440 just fine. Now when I try, the screen goes black and I have to revert to a lower resolution. The highest it will go now is 2560 x 1080. Lower resolutions work fine as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 12 08:56:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2258] InstallationDate: Installed on 2019-02-19 (173 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7S01200 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET53W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7S01200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7S01200 dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839817] Re: External monitors does not work anymore 5.0.0-21-generic
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839817 Title: External monitors does not work anymore 5.0.0-21-generic Status in linux package in Ubuntu: Confirmed Bug description: I am using a USB-C docking station for my laptop. It does not react to a displayport cable at all. If I enter the console (ctrl-alt-f1), connect a HDMI cable, then return to the GUI (ctrl-alt-f7) it will briefly detect the monitor. As soon as I try to switch to it, it loses the connection (can I get logs for this somehow?). Symptoms same as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663 Not sure if I can downgrade to the suggested 4.15.0-45-generic from my current kernel without issues to test if that solves the issue for me. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ms 2186 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 12 10:42:06 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=e27c1b67-65d9-4474-932c-d2e2df016768 InstallationDate: Installed on 2018-03-29 (501 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=17864c9e-f927-45a4-9b3a-f2b36fc46916 ro locale=en_US quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-23 (111 days ago) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 06CC14 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1766398 Title: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] On this Dell machine (codename: turtle bay), the microphone always shows up in the sound-setting even there is no microphone plugged in. [Fix] Without this fix, the pin will be regarded as microphone, and the jack name is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged into the jack. So the UI is confusing to users since the microphone always shows up in the UI even there is no microphone plugged. After adding this flag, the jack name is "Headset Mic Phantom", then the pulseaudio can handle its detection correctly. [Test Case] After booting up the system, and without plugging anything in the audio combo jack, there is nothing in the input tab of sound-setting, then plug a headset in the jack, the what-did-you-plug-in dialogue pops up, users can select headset mic from UI, and headset-mic shows up in the sound-setting, we can record sound via headset-mic [Regression Potential] Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC which is only used by Dell precision 3630 by now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1766398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772787] Re: lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772787 Title: lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel Status in linux package in Ubuntu: Invalid Bug description: Execute lspci command in ubuntu 16.04.4 with kernel update (kernel:4.10.0-40-generic), but always prompt error that cannot open /sys/bus/pci/devices/0001:00:02.0/resource: no such file or directory. Execute lspci command in ubuntu 16.04.4 without kernel update (kernel:4.4.0-116-generic), issue not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767133 Title: linux-image-4.15.0-20-generic install after upgrade from xenial breaks Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-hwe-edge source package in Bionic: Invalid Bug description: [Impact] Some upgrades from xenial to bionic break. [Test Case] Change sources.list from xenial to bionic, then apt install linux-image-4.15.0-20-generic. [Regression Potential] The kernel may be uninstallable if there is no linux-base with the appropriate version in the archive. When installing the linux-image-4.15.0-20-generic kernel from bionic on xenial breaks because of the unversioned Depends on linux-base. /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: linux-update-symlinks: not found dpkg: error processing package linux-image-4.15.0-20-generic (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: linux-image-4.15.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) If the trigger is called, when some meta packages are installed, it won't happen. If all packages are upgraded, it's possible linux-base is going to be upgraded first, so the problem won't happen either. So, not all upgrades will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767992] Re: Linux md raid-10 freezes during resync
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * If regular and resync IO happen at the same time during a regular IO split, the split bio will wait until resync IO finishes while at the same time the resync IO is waiting for regular IO to finish. This results in deadlock. * I believe this only impacts Bionic as Disco+ already contains this commit. Xenial doesn't contain the commit that this one fixes. [Test Case] The test kernel containing this commit received positive feedback in the launchpad bug. From the launchpad bug comment #10: "For reproduce on 4.15.0-50-generic: Make new raid-10, add some io fio/dd, unpack anaconda archives, after minute or two deadlocked" [Regression Potential] * This fix has been in mainline since December 2018 and I don't see any fixup commits upstream referencing this one. The small number of changes in this commit seem reasonable for managing the `nr_pending` adjustments which preclude either regular or resync IO. Original bug description follows: - I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949] __schedule+0x297/0x8b0 [ 2659.317954] schedule+0x2c/0x80 [ 2659.317959] raise_barrier+0xa1/0x1a0 [raid10] [ 2659.317963] ? wait_woken+0x80/0x80 [ 2659.317968] raid10_sync_request+0x205/0x1f10 [raid10] [ 2659.317975] ? find_next_bit+0xb/0x10 [ 2659.317980] ? cpumask_next+0x1b/0x20 [ 2659.317985] ? is_mddev_idle+0x92/0xf4 [ 2659.317990] md_do_sync+0x8ca/0xf10 [ 2659.317994] ? wait_woken+0x80/0x80 [ 2659.318000] md_thread+0x129/0x170 [ 2659.318004] ?
[Kernel-packages] [Bug 1806751] Re: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to install/upgrade: installed linux-headers-4.15.0-42-generic package post-installation script subproces
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806751
Title:
package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Confirmed
Bug description:
installing 18.4 over 16.8
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-42-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3220 Analog [ALC3220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: george 1835 F pulseaudio
/dev/snd/controlC0: george 1835 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfb32 irq 45'
Mixer name : 'Realtek ALC3220'
Components : 'HDA:10ec0280,102805d2,0013'
Controls : 25
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 46'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10de094c,00100100'
Controls : 21
Simple ctrls : 3
Date: Tue Dec 4 12:39:55 2018
ErrorMessage: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=298e362b-64c7-442b-9eb9-dd4ac8caecf7
InstallationDate: Installed on 2017-06-17 (535 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: Dell Inc. Precision T3610
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-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.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-4.15.0-42-generic 4.15.0-42.45 failed to
install/upgrade: installed linux-headers-4.15.0-42-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago)
dmi.bios.date: 02/28/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/28/2014:svnDellInc.:pnPrecisionT3610:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T3610
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1806850 Title: Fix Terminus USB hub that may breaks connected USB devices after S3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] USB devices connected to Terminus USB hub stop working after S3. [Fix] The Terminus hub seems to have a rather slow reset command, so we need to wait for extra time before doing any further action. [Test] After applying the fix, USB devices connected to the HUB no longer stop functioning after S3. [Regression Potential] Low. Although the fix affects all devices connect to the HUB, it has no functional change other than imposes longer delay time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806676] Re: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current st
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806676 Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: Problem during a update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-131 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hh 2768 F pulseaudio Date: Tue Dec 4 10:10:48 2018 DuplicateSignature: package:linux-headers-4.4.0-131:4.4.0-131.157 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package linux-headers-4.4.0-131 (--configure): package linux-headers-4.4.0-131 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=dfd3208c-bc79-4149-a7e7-7f455f6f5a92 InstallationDate: Installed on 2017-07-08 (513 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=4d9e2819-1e05-4805-99dc-8791af5ca4c5 ro 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.19 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-131 4.4.0-131.157 failed to install/upgrade: package linux-headers-4.4.0-131 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807341 Title: ubuntu_squashfs_smoke_test failed with Disco Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Tested on a KVM node with generic kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh Testing with compression method gzip Testing mount of squashfs: PASSED (gzip) Testing umount of squashfs: PASSED (gzip) Checking data integrity: FAILED (squashed /bin different from original /bin, gzip) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 07:39 seq crw-rw 1 root audio 116, 33 Dec 7 07:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Dec 7 07:44:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1807341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807155] Re: Laptop doesn't wake up from deep sleep.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807155 Title: Laptop doesn't wake up from deep sleep. Status in linux package in Ubuntu: Confirmed Bug description: While on battery power, Asus Zenbook UX461U laptop can't wake up from suspend with mem_sleep_default=deep kernel option. Upon opening the lid or pressing the power button the power LED switches from blinking to constant light, the keyboard LEDs blink instantly, but nothing more happens. Apart from the power LED the laptop doesn't show any signs of operation. The keyboard backlight doesn't work. The only way out of this state is powering the laptop off by long pressing the power button. On AC power, the laptop resumes from deep sleep normally. Deep sleep is crucial, because without the mem_sleep_default=deep option battery drain is very high (several percent per hour). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misha 2527 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 16:24:58 2018 HibernationDevice: RESUME=UUID=28642731-be8e-4c6b-9cfe-74d637c87bf0 InstallationDate: Installed on 2018-07-30 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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 13d3:56a2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX461UA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-12-01 (5 days ago) dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461UA.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461UA.312:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnUX461UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX461UA 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/1807155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: 4 tests failed: [11] ftrace - function glob filters [FAIL] [23] Kprobe event argument syntax [FAIL] [36] event trigger - test histogram trigger [FAIL] [51] (instance) event trigger - test histogram trigger [FAIL] With the test suite in the upstream kernel tree, 3 of these failures can be reproduced, except this one: -e -n [34] Kprobe event argument syntax -e[UNTESTED] $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' TAP version 13 selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] event tracing - enable/disable with event level files [PASS] [6] event tracing - restricts events based on pid [PASS] [7] event tracing - enable/disable with subsystem level files [PASS] [8] event tracing - enable/disable with top level files [PASS] [9] ftrace - function graph filters with stack tracer [PASS] [10] ftrace - function graph filters [PASS] [11] ftrace - function glob filters [FAIL] [12] ftrace - function pid filters[PASS] [13] ftrace - test for function event triggers[PASS] [14] ftrace - function profiler with function tracing [PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances[PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument[UNTESTED] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer[PASS] [27] Kprobe dynamic event - probing module[PASS] [28] Kretprobe dynamic event with arguments [PASS] [29] Kretprobe dynamic event with maxactive [PASS] [30] Register/unregister many kprobe events [PASS] [31] Kprobe events - probe points [PASS] [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED] [33] event trigger - test event enable/disable trigger[PASS] [34] event trigger - test trigger filter [PASS] [35] event trigger - test histogram modifiers [PASS] [36] event trigger - test histogram trigger [FAIL] [37] event trigger - test multiple histogram triggers [PASS] [38] event trigger - test snapshot-trigger[PASS] [39] event trigger - test stacktrace-trigger [PASS] [40] event trigger - test traceon/off trigger [PASS] [41] (instance) Basic test for tracers [PASS] [42] (instance) Basic trace clock test [PASS] [43] (instance) event tracing - enable/disable with event level files [PASS] [44] (instance) event tracing - restricts events based on pid[PASS] [45] (instance) event tracing - enable/disable with subsystem level files [PASS] [46] (instance) ftrace - test for function event triggers[PASS] [47] (instance) ftrace - test for function traceon/off triggers [PASS] [48] (instance) event trigger - test event enable/disable trigger[PASS] [49] (instance) event trigger - test trigger filter [PASS] [50] (instance) event trigger - test histogram modifiers [PASS] [51] (instance) event trigger - test histogram trigger [FAIL] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 46 # of failed: 4 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL] make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1809701] Re: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809701 Title: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Confirmed Bug description: Test failed with "Operation not supported" when trying to offline a CPU: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online This issue cannot be reproduced on CaviumThunderX ARM64 server, just the moonshots. $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 8132's current affinity mask: ff pid 8132's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-7 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 7 ./cpu-on-off-test.sh: line 92: echo: write error: Operation not supported offline_cpu_expect_success 7: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/linux/tools/testing/selftests' The CPU hotplug config was enabled on this SUT: $ cat /boot/config-`uname -r` | grep HOTPLUG | grep CPU CONFIG_HOTPLUG_CPU=y CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 25 04:01 seq crw-rw 1 root audio 116, 33 Dec 25 04:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Dec 25 04:54:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794169 Title: AWS ubuntu became unreachable after ssh login Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I've reached strange situation with Ubuntu 18.04 LTS with latest kernel on AWS m5.xlarge instance. System became unreachable after series of successful ssh logins. systemd -user became zombie and block main systemd daemon (PID 1). I've created bug https://github.com/systemd/systemd/issues/10123 but it was closed with "there's a problem with your kernel". https://github.com/systemd/systemd/issues/10123#issuecomment-423984751 Symptoms are very similar to https://github.com/systemd/systemd/issues/8598 apetren+ 26679 0.0 0.0 0 0 ?Z02:56 0:00 \_ [(sd-pam)] apetren+ 26855 0.0 0.0 76636 7816 ?Ds 02:57 0:00 /lib/systemd/systemd --user apetren+ 26856 0.0 0.0 0 0 ?Z02:57 0:00 \_ [(sd-pam)] apetren+ 26954 0.0 0.0 0 0 ?Zs 02:57 0:00 \_ [kill] apetren+ 27053 0.0 0.0 76636 7496 ?Ss 02:58 0:00 /lib/systemd/systemd --user apetren+ 27054 0.0 0.0 193972 2768 ?S02:58 0:00 \_ (sd-pam) This situation is repeatable on 7 instances 1-2 times per week. how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image 2. update kernel and packages to latest version 3. from another instance run while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep defunc |grep -v grep" ; done By this command in couple of days I have 2->4->6->8... zombies and in a hour system is frozen... sudo reboot is not working, because systemd with PID 1 is unreachable. kill -9 1 -- not working as well. # uname -r: Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" # systemd --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid AWS instance m5.xlarge Please let me know if you need any information. --- ProblemType: Bug 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': 'aplay' ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-91caece9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2b Ec2InstanceType: m5.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.xlarge Package: systemd 237-3ubuntu10.3 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-aws N/A linux-backports-modules-4.15.0-1021-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1021-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-02cfe7fcd8a997085 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795598] Re: linux: -proposed tracker
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795598 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid 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: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795486] Re: Cosmic update to 4.18.11 stable release
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795486 Title: Cosmic update to 4.18.11 stable release Status in linux package in Ubuntu: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.18.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.18.11 stable release shall be applied: Linux 4.18.11 spi: Fix double IDR allocation with DT aliases iw_cxgb4: only allow 1 flush on user qps vmw_balloon: include asm/io.h sched/fair: Fix vruntime_normalized() for remote non-migration wakeup ext4, dax: set ext4_dax_aops for dax files ext4, dax: add ext4_bmap to ext4_dax_aops ext4: show test_dummy_encryption mount option in /proc/mounts ext4: don't mark mmp buffer head dirty ext4: fix online resizing for bigalloc file systems with a 1k block size ext4: fix online resize's handling of a too-small final block group ext4: recalucate superblock checksum after updating free blocks/inodes ext4: avoid arithemetic overflow that can trigger a BUG ext4: avoid divide by zero fault when deleting corrupted inline directories ext4: check to make sure the rename(2)'s destination is not freed tty: vt_ioctl: fix potential Spectre v1 drm/amdgpu: add new polaris pci id drm: udl: Destroy framebuffer only if it was initialized drm/vc4: Fix the "no scaling" case on multi-planar YUV formats drm/nouveau/drm/nouveau: Prevent handling ACPI HPD events too early drm/nouveau/drm/nouveau: Use pm_runtime_get_noresume() in connector_detect() drm/nouveau/drm/nouveau: Fix deadlock with fb_helper with async RPM requests drm/nouveau/drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau/drm/nouveau: Don't forget to cancel hpd_work on suspend/unload drm/nouveau: Fix deadlocks in nouveau_connector_detect() drm/nouveau: Remove duplicate poll_enable() in pmops_runtime_suspend() drm/nouveau: Only write DP_MSTM_CTRL when needed drm/nouveau: Reset MST branching unit before enabling drm/i915/bdw: Increase IPS disable timeout to 100ms ocfs2: fix ocfs2 read block panic libata: mask swap internal and hardware tag Revert "ubifs: xattr: Don't operate on deleted inodes" scsi: target: iscsi: Use bin2hex instead of a re-implementation scsi: target: iscsi: Use hex2bin instead of a re-implementation Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name" bpf/verifier: disallow pointer subtraction Revert "rpmsg: core: add support to power domains for devices" mm: shmem.c: Correctly annotate new inodes for lockdep mm: disable deferred struct page for 32-bit arches fork: report pid exhaustion correctly crypto: x86/aegis,morus - Do not require OSXSAVE for SSE2 ring-buffer: Allow for rescheduling when removing pages Revert "PCI: Add ACS quirk for Intel 300 series" spi: fix IDR collision on systems with both fixed and dynamic SPI bus numbers xen/x86/vpmu: Zero struct pt_regs before calling into sample handling code xen/netfront: don't bug in case of too many frags platform/x86: alienware-wmi: Correct a memory leak platform/x86: dell-smbios-wmi: Correct a memory leak mtd: rawnand: denali: fix a race condition when DMA is kicked mtd: devices: m25p80: Make sure the buffer passed in op is DMA-able ALSA: oxfw: fix memory leak of private data ALSA: oxfw: fix memory leak of discovered stream formats at error path ALSA: oxfw: fix memory leak for model-dependent data at error path ALSA: fireworks: fix memory leak of response buffer at error path ALSA: firewire-tascam: fix memory leak of private data ALSA: firewire-digi00x: fix memory leak of private data ALSA: fireface: fix memory leak in ff400_switch_fetching_mode() ALSA: emu10k1: fix possible info leak to userspace on SNDRV_EMU10K1_IOCTL_INFO ALSA: bebob: use address returned by kmalloc() instead of kernel stack for streaming DMA mapping ALSA: bebob: fix memory leak for M-Audio FW1814 and ProjectMix I/O at error path ASoC: uapi: fix sound/skl-tplg-interface.h userspace compilation errors ASoC: rsnd: fixup not to call clk_get/set under non-atomic ASoC: tas6424: Save last fault register even when clear ASoC: cs4265: fix MMTLR Data switch control ASoC: wm9712: fix replace codec to component NFC: Fix the number of pipes NFC: Fix possible memory corruption when handling SHDLC I-Frame
[Kernel-packages] [Bug 1794318] Re: unable to boot after installing vagrant
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant Status in vagrant: New Status in linux package in Ubuntu: Incomplete Status in mdadm package in Ubuntu: Incomplete Bug description: Reproduction steps: clean install of kubuntu & reboot full update & reboot apt-get install vagrant & reboot =>busybox My system won't boot after installing vagrant. When I switch back to the previous kernel version it works until another update-initramfs. Currently I'm using 2 ssd's for intel fake raid 1(mirror) for kubuntu 18.04 I've reinstalled my system multiple times. I can reproduce this issue every time. To manage notifications about this bug go to: https://bugs.launchpad.net/vagrant/+bug/1794318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795582] Re: linux: 4.4.0-138.164 -proposed tracker
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795582 Title: linux: 4.4.0-138.164 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released 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: bug 1795583 (linux-aws), bug 1795584 (linux-lts-xenial) derivatives: bug 1795585 (linux-aws), bug 1795586 (linux-euclid), bug 1795589 (linux-kvm), bug 1795591 (linux-raspi2), bug 1795593 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on X/B
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786729
Title:
execveat03 in ubuntu_ltp_syscalls failed on X/B
Status in ubuntu-kernel-tests:
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 Bionic:
Fix Released
Bug description:
== Justification ==
The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
("Introduce v3 namespaced file capabilities"), should use
d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
correctly. This is needed, for example, if execveat() is called with an
open but unlinked overlayfs file, because overlayfs unhashes dentry on
unlink.
This is a regression of real life application, first reported at
https://www.spinics.net/lists/linux-unionfs/msg05363.html
With the execveat03 test in the LTP test suite on an affected kernel, it will
fail with:
<<>>
tag=execveat03 stime=1534135632
cmdline="execveat03"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL
Summary:
passed 0
failed 1
skipped 0
warnings 0
== Fix ==
355139a8 (cap_inode_getsecurity: use d_find_any_alias() instead of
d_find_alias())
It can be cherry-picked for Bionic, but it needs to be backported to
Xenial along with the logic when we backport 8db6c34f1dbc (bug
1778286).
The test kernel for Xenial / Bionic could be found here:
http://people.canonical.com/~phlin/kernel/lp-1786729-execveat03/
This patch has already been cherry-picked into Cosmic and Unstable.
== Regression Potential ==
Low, this patch just uses a correct function to handle unhashed dentry, and
it's been applied in both upstream and our newer kernel.
== Test Case ==
Run the reproducer in the commit message, or,
run the execveat03 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
Uname: Linux 4.4.0-1064-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 13 04:51:09 2018
Ec2AMI: ami-529fb82a
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: x1e.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794480] Re: [18.10 - FEAT] NVMe kdump support
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794480 Title: [18.10 - FEAT] NVMe kdump support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Enable kdump to dump from NVMe storage. This feature is for Release Note update only. No addl. code is required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794995] Re: 18.04 can't adjust brightness on ASUS T300F. Worked fine on 16.04.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794995 Title: 18.04 can't adjust brightness on ASUS T300F. Worked fine on 16.04. Status in linux package in Ubuntu: Invalid Bug description: Title of my display under Settings is "Unknown Display". I think there's no proper display driver for my laptop in this new distribution, "18.04", because the setting for my display works fine before I upgrade from 16.04. While I said "works fine", I meant, I could use the "fn" button plus with the brightness adjusting button, which is "f5" and "f6" on my laptop, to adjust the brightness. Other than the "fn" combination button not working, I can't even adjust the brightness in the setting and inside the main menu bar, which I think there might have since a control center is one of the features of this version upgrade. So, thanks for reading my problem, and please help, otherwise, it's so unhealthy for my eyes for looking at a screen with too bright for so long and I have to look at the screen for so long. Thanks in advance. Ps, in case it's needed, the model of my laptop is, ASUS T300F. A transform 2-in-one laptop. The fact that my laptop can "transform" might be the reason why I got this issue, the drive that serves all just fail to meet its needs. I'm sorry. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 28 21:44:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (177 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA 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.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 21:43:24 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806852] Re: the 4.15.0.42 kernel causes a slower PC
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806852 Title: the 4.15.0.42 kernel causes a slower PC Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: kernel(64bits) 4.15.0.42 causes a slowdown of the PC, reduces the size of the display, and a blocking if I try to run "NVIDIA X Server Settings". If I chose the kernel 4.15.0.39 at startup the operation of ubuntu is normal. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jojo 1715 F pulseaudio /dev/snd/controlC0: jojo 1715 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5bc4301e-f8ce-487d-a740-e39dfd66f73a InstallationDate: Installed on 2017-04-15 (598 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: lono wireless extensions. enp1s7no wireless extensions. enp0s10 no wireless extensions. Lsusb: Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=UUID=6bef0add-9945-4094-b0b2-c7c5ebc3d17a ro ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-07 (211 days ago) UserGroups: adm audio cdrom dialout disk plugdev scanner sudo tty wireshark _MarkForUpload: True dmi.bios.date: 01/13/2006 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-K8NF-9 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8NF-9:rvrx.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729637
Title:
Samba mount/umount in docker container triggers kernel Oops
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
== SRU Justification ==
This bug causes Samba mount and umounts in docker container to trigger
a kernel Oops. When running 2 docker containers, one as samba server and
another one as samba client that mounts and umounts a smb share a kernel
OOps can be triggered.
This bug happens in Xenial and Zesty, and is fixed by the following two
commits:
76da0704507b ("ipv6: only call ip6_route_dev_notify() once for
NETDEV_UNREGISTER")
12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")
Both commits are clean cherry picks. 76da0704507b is in mainline as of v4.12.
Commit 12d94a804946 is in mainline as of v4.13-rc6.
== Fixes ==
commit 76da0704507bbc51875013f6557877ab308cfd0a
Author: WANG Cong
Date: Tue Jun 20 11:42:27 2017 -0700
ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
commit 12d94a804946af291e24b80fc53ec86264765781
Author: Eric Dumazet
Date: Tue Aug 15 04:09:51 2017 -0700
ipv6: fix NULL dereference in ip6_route_dev_notify()
== Regression Potential ==
Both commits are specific to ipv6 and fix a regression introduced into Xenial
and Zesty.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at:
https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation
with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running
multiple docker containers with Nginx or small network applications in
parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count
= 1" messages are related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 3 09:51 seq
crw-rw 1 root audio 116, 33 Nov 3 09:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y
console=ttyS0
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-37-generic N/A
linux-backports-modules-4.10.0-37-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images
Uname: Linux 4.10.0-37-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias:
[Kernel-packages] [Bug 1789518] Re: automounting MTP or USB storage devices no longer works.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789518 Title: automounting MTP or USB storage devices no longer works. Status in linux package in Ubuntu: Invalid Bug description: After upgrading from xenial to bionic, USB (both MTP and mass storage) devices will not automount. syslog shows the usb device is found and recognized as a storage device: Aug 28 16:49:18 insitu kernel: [ 4412.072025] usb 1-8: new high-speed USB device number 18 using ehci-pci Aug 28 16:49:19 insitu kernel: [ 4412.229198] usb 1-8: New USB device found, idVendor=0421, idProduct=01c7 Aug 28 16:49:19 insitu kernel: [ 4412.229202] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 28 16:49:19 insitu kernel: [ 4412.229204] usb 1-8: Product: N900 (Storage Mode) Aug 28 16:49:19 insitu kernel: [ 4412.229206] usb 1-8: Manufacturer: Nokia Aug 28 16:49:19 insitu kernel: [ 4412.229211] usb 1-8: SerialNumber: 372041756775 Aug 28 16:49:19 insitu kernel: [ 4412.231642] usb-storage 1-8:1.0: USB Mass Storage device detected Aug 28 16:49:19 insitu kernel: [ 4412.233887] scsi host7: usb-storage 1-8:1.0 Aug 28 16:49:19 insitu mtp-probe: checking bus 1, device 18: "/sys/devices/pci:00/:00:10.4/usb1/1-8" Aug 28 16:49:19 insitu mtp-probe: bus: 1, device: 18 was not an MTP device Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on /sys/devices/pci:00/:00:10.4/usb1/1-8/1-8:1.0 Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on /sys/devices/pci:00/:00:10.4/usb1/1-8 Aug 28 16:49:20 insitu kernel: [ 4413.251860] scsi 7:0:0:0: Direct-Access NokiaN900 031 PQ: 0 ANSI: 2 Aug 28 16:49:20 insitu kernel: [ 4413.252743] scsi 7:0:0:1: Direct-Access NokiaN900 031 PQ: 0 ANSI: 2 Aug 28 16:49:20 insitu kernel: [ 4413.254638] sd 7:0:0:0: Attached scsi generic sg3 type 0 Aug 28 16:49:20 insitu kernel: [ 4413.254946] sd 7:0:0:1: Attached scsi generic sg4 type 0 Aug 28 16:49:20 insitu kernel: [ 4413.255201] sd 7:0:0:0: Power-on or device reset occurred Aug 28 16:49:20 insitu kernel: [ 4413.255822] sd 7:0:0:1: Power-on or device reset occurred Aug 28 16:49:20 insitu kernel: [ 4413.260481] sd 7:0:0:1: [sdd] Attached SCSI removable disk Aug 28 16:49:20 insitu kernel: [ 4413.261109] sd 7:0:0:0: [sdc] Attached SCSI removable disk Aug 28 16:49:26 insitu kernel: [ 4419.523221] sd 7:0:0:0: [sdc] 56631296 512-byte logical blocks: (29.0 GB/27.0 GiB) Aug 28 16:49:26 insitu kernel: [ 4419.523952] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 28 16:49:26 insitu kernel: [ 4419.719652] sdc: sdc is never mounted; I can mount it manually with: sudo mount /dev/sdc /mnt/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1490 F pulseaudio CurrentDesktop: XFCE Date: Tue Aug 28 16:45:48 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=13df1544-3ecd-4a0b-bea6-347f3f27871d HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2010-11-05 (2853 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago) dmi.bios.date: 10/06/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1015.002 dmi.board.name: A8V Deluxe 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.:bvr1015.002:bd10/06/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: To Be Filled By
[Kernel-packages] [Bug 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1622 F pulseaudio /dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio /dev/snd/controlC1: mate 1622 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (41 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-27 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799467] Re: [19.04 FEAT| Enable virtio-gpu for s390x
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799467 Title: [19.04 FEAT| Enable virtio-gpu for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Allows to administer s390x KVM guests with the tools typically used for x86 guests. E.g., guest administrators connecting from a Windows client can use the virt-manager UI. The code is upstream with kernel 4.17 579f1a2 s390/setup : enable display support for KVM guest aa0f2dd s390/char : Rename EBCDIC keymap variables 0a3994f Kconfig : Remove HAS_IOMEM dependency for Graphics support Code already available, only kernel configs need to be checked. In addition following kernel configs need to be set CONFIG_DRM CONFIG_DUMMY_CONSOLE CONFIG_FB CONFIG_FRAMEBUFFER_CONSOLE CONFIG_VIRTIO_INPUT CONFIG_INPUT CONFIG_INPUT_EVDEV CONFIG_DRM_VIRTIO_GPU CONFIG_VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1799467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802585
Title:
NFS v4.0: Stale data after file is renamed while another process has
an open file handle
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Bug description:
NOTE: This bug has been fixed in the upstream mainline kernel via
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
and merged in the latest NFS client patches in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.
The full patchset is here: https://marc.info/?l=linux-
nfs=153816500525563=2
I'm repeating the report I sent to the NFS maintainers on the mailing
list:
On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
stale data is shown if a file remains open on one machine, and the
file is overwritten via a rename() on another. Here's my test:
1. On node A, create two different files on a shared NFS mount:
"test1.txt" and "test2.txt".
2. On node B, continuously show the contents of the first file: "while
true; do cat test1.txt; done"
3. On node B, run a process that keeps "test1.txt" open. For example,
with Python, run:
f = open('/nfs-mount/test1.txt', 'r')
4. Rename test2.txt via "mv -f test2.txt test1.txt"
On node B, I see the contents of the original test1.txt indefinitely,
even after I disabled attribute caching and the lookup cache. I can
make the while loop in step 2 show the new content if I perform one of
these actions:
1. Run "ls /nfs-mount"
2. Close the open file in step 3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789018] Re: /sys/power/state miss "disk"
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789018 Title: /sys/power/state miss "disk" Status in linux package in Ubuntu: Invalid Bug description: cat /sys/power/state freeze mem As a result, hibernate-disk is failed to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ming 1501 F pulseaudio CurrentDesktop: XFCE Date: Sat Aug 25 22:42:04 2018 HibernationDevice: RESUME=UUID=6c3eb510-861e-4d9a-9009-0c5b62d57105 InstallationDate: Installed on 2018-08-11 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0570 LighTuning Technology Inc. Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-54 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=8e486299-4bbf-4041-8cae-502b7f7e6c5c ro splash resume=UUID=6c3eb510-861e-4d9a-9009-0c5b62d57105 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd05/25/2018:svnAcer:pnSwiftSF314-54:pvrV1.07:rvnKBL:rnStrongbow_KL:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802480] Re: Crash when using IPsec VTI interfaces on 4.15 and 4.18.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802480 Title: Crash when using IPsec VTI interfaces on 4.15 and 4.18. Status in linux package in Ubuntu: Confirmed Bug description: Hey! After upgrading a few VPN to 4.15.0-38.41 (either Xenial or Bionic), we get random crashes. This also happens with the 4.18 in bionic- proposed. These crashes didn't happen with 4.4 from Xenial. Here is a stack trace: [ 31.154360] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 31.162233] PGD 0 P4D 0 [ 31.164786] Oops: [#1] SMP PTI [ 31.168291] CPU: 5 PID: 42 Comm: ksoftirqd/5 Not tainted 4.18.0-11-generic #12~18.04.1-Ubuntu [ 31.176854] Hardware name: Supermicro Super Server/X10SDV-4C-7TP4F, BIOS 1.0b 11/21/2016 [ 31.184980] RIP: 0010:vti_rcv_cb+0xb9/0x1a0 [ip_vti] [ 31.189962] Code: 8b 44 24 70 0f c8 89 87 b4 00 00 00 48 8b 86 20 05 00 00 8b 80 f8 14 00 00 85 c0 75 05 48 85 d2 74 0e 48 8b 43 58 48 83 e0 fe 40 38 04 74 7d 44 89 b3 b4 00 00 00 49 8b 44 24 20 48 39 86 20 [ 31.208916] RSP: 0018:bc61832e3920 EFLAGS: 00010246 [ 31.214160] RAX: RBX: 9a3504964a00 RCX: 0002 [ 31.221328] RDX: 9a351add4080 RSI: 9a351aa08000 RDI: 9a3504964a00 [ 31.228485] RBP: bc61832e3940 R08: 0004 R09: c0aa612b [ 31.235643] R10: 0008f09b99881884 R11: 1884bd4e2d6b1fac R12: 9a3507b31900 [ 31.242803] R13: 9a3507b31000 R14: R15: 9a3504964a00 [ 31.249964] FS: () GS:9a35bfd4() knlGS: [ 31.258077] CS: 0010 DS: ES: CR0: 80050033 [ 31.263848] CR2: 0038 CR3: 00041a40a003 CR4: 003606e0 [ 31.271004] DR0: DR1: DR2: [ 31.278163] DR3: DR6: fffe0ff0 DR7: 0400 [ 31.285320] Call Trace: [ 31.287789] xfrm4_rcv_cb+0x4a/0x70 [ 31.291297] xfrm_input+0x58f/0x8f0 [ 31.294807] vti_input+0xaa/0x110 [ip_vti] [ 31.298926] vti_rcv+0x33/0x3c [ip_vti] [ 31.302783] xfrm4_esp_rcv+0x39/0x50 [ 31.306375] ip_local_deliver_finish+0x62/0x200 [ 31.310923] ip_local_deliver+0xdf/0xf0 [ 31.314775] ? ip_rcv_finish+0x420/0x420 [ 31.318718] ip_rcv_finish+0x126/0x420 [ 31.322486] ip_rcv+0x28f/0x360 [ 31.325655] ? inet_del_offload+0x40/0x40 [ 31.329686] __netif_receive_skb_core+0x48c/0xb70 [ 31.334413] ? kmem_cache_alloc+0xb4/0x1d0 [ 31.338532] ? __build_skb+0x2b/0xf0 [ 31.342128] __netif_receive_skb+0x18/0x60 [ 31.346244] ? __netif_receive_skb+0x18/0x60 [ 31.350536] netif_receive_skb_internal+0x45/0xe0 [ 31.355263] napi_gro_receive+0xc5/0xf0 [ 31.359141] mlx5e_handle_rx_cqe+0x1b2/0x5d0 [mlx5_core] [ 31.364476] ? skb_release_all+0x24/0x30 [ 31.368430] mlx5e_poll_rx_cq+0xd3/0x990 [mlx5_core] [ 31.373432] mlx5e_napi_poll+0x9b/0xc60 [mlx5_core] [ 31.378333] ? __switch_to_asm+0x34/0x70 [ 31.382270] ? __switch_to_asm+0x40/0x70 [ 31.386214] ? __switch_to_asm+0x34/0x70 [ 31.391056] ? __switch_to_asm+0x40/0x70 [ 31.395905] ? __switch_to_asm+0x34/0x70 [ 31.400743] net_rx_action+0x140/0x3a0 [ 31.405379] ? __switch_to+0xad/0x500 [ 31.409887] __do_softirq+0xe4/0x2bb [ 31.414448] run_ksoftirqd+0x2b/0x40 [ 31.418862] smpboot_thread_fn+0xfc/0x170 [ 31.423700] kthread+0x121/0x140 [ 31.427701] ? sort_range+0x30/0x30 [ 31.432040] ? kthread_create_worker_on_cpu+0x70/0x70 [ 31.437816] ret_from_fork+0x35/0x40 [ 31.442219] Modules linked in: esp6 authenc echainiv xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo ip_vti ip_tunnel ip6_vti ip6_tunnel tunnel6 8021q garp mrp stp llc bonding ipt_REJECT nf_reject_ipv4 nfnetlink_log n fnetlink xt_NFLOG xt_hl xt_limit xt_nat xt_TCPMSS xt_HL xt_comment xt_tcpudp xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_connmark xt_mark iptable_mangle xt_CT nf_conntrack xt_addrtype iptable_raw bpfilter ipmi_ssif gpio_ ich intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds joydev mei_me intel_pch_thermal ioatdma mei lpc_ich ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid sch_fq_codel [ 31.519488] ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear mlx5_ib ib_uverbs ib _core raid1 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul
[Kernel-packages] [Bug 1802666] Re: Same as bug 1800238
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1802666 Title: Same as bug 1800238 Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: With kernel 4.15 Ubuntu 18.04, I could display the tv stations with VLC. Not with kernel 4.18. As a second OS I have Linux Mint 19 (kernel 4.15), there everything works. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1411 F pulseaudio /dev/snd/controlC1: ed 1411 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-22 (19 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=4508126b-278d-4ffb-a672-c6f0f2bb0827 ro elevator=deadline quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1802666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773000] Re: [18.04] [regression testing] ubuntu_bpf tests failing on amd64
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773000 Title: [18.04] [regression testing] ubuntu_bpf tests failing on amd64 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: For example: http://10.246.72.4/test- results/4.15.0-21.22-generic/ubuntu_bpf-4.15.0-21.22-amd64-index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1773000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729849] Re: mkfs.xfs complains about /dev/sdb2 is busy on Xenial
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729849 Title: mkfs.xfs complains about /dev/sdb2 is busy on Xenial Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This issue is reproducible on two different nodes in our testpool, fozzie and rizzo, both with 4.4.0-98-generic amd64. On a clean install system with a scratch drive sdb available. Steps: 1. sudo parted /dev/sdb mklabel -s gpt 2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB 3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB 4. sudo mkfs.xfs -f /dev/sdb1 5. sudo mkfs.xfs -f /dev/sdb2 Result: mkfs.xfs: cannot open /dev/sdb2: Device or resource busy In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will fail with this. And this happens on both nodes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 12:07 seq crw-rw 1 root audio 116, 33 Nov 3 12:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 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: Fri Nov 3 12:37:59 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1729849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775065] Re: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775065 Title: No brightness controls and /sys/class/backlight empty after upgrade to Bionic on laptop with GeForce GTX 1060 Mobile (kernel parameter acpi_osi= is a workaround) Status in linux package in Ubuntu: Confirmed Bug description: This is a case of "Backlight control does not work, and there are no entries in /sys/class/backlight" for what lspci reports as "NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)" where the kernel parameter acpi_osi= is a workaround. (The workaround is also recorded on Ask Ubuntu at https://askubuntu.com/questions/1030526 /brightness-on-laptop-msi-gt72vr-in-ubuntu-18-04-with-nvidia-gtx-1060 -mobile-does/1043598#1043598.) The problem is new for me after upgrade to Bionic, although the cause might be the corresponding update to the NVIDIA drivers. I will add attachments following the instructions at https://wiki.ubuntu.com/Kernel/Debugging/Backlight, though most of them seem to be uninteresting. If I can provide further information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 4 14:20:34 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-04 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgarvin2442 F pulseaudio /dev/snd/controlC0: bgarvin2442 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1b60cccb-eea7-4d0b-a32b-97d236a5177f Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=557ebdfc-3380-4721-a494-65c34cb70b2f ro i8042.nomux i8042.reset acpi_osi= ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-04 (1 days ago) UserGroups: adm lpadmin sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76, Inc. dmi.board.version: oryp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03RSA:bd09/08/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2:rvnSystem76,Inc.:rnOryxPro:rvroryp2:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp2 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Invalid Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796640] Re: linux: -proposed tracker
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796640 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: derivatives: bug 1796641 (linux-oem) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Realtek 8723be's ant_sel parameter stops working since 4.15.0-33.36. [Fix] The commit that causes the regression works in mainline, so there are some functional dependencies are not in 4.15. Finding those dependencies can be hard since I don't have the hardware to test with, also pulling new commits may cause new regression. So the safest way to deal with this bug is to simply revert the regression commit. [Test] User confirmed reverting the commit can fix the issue. [Regression Potential] Low. Realtek 8723be works without this commit. === Original Bug Report === When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802691 Title: Slow send speed with Intel I219-V on Ubuntu 18.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Testing with iperf3 send speed is only 750mbps while receive speed is normal - 940mbps. Ubuntu 18.04.1 Msi b250m mortar --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 1016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-09 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A69 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: B250M MORTAR ARCTIC (MS-7A69) 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.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A69 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/1802691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802810] Re: SD card reader not working on Ubuntu 18.10
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802810 Title: SD card reader not working on Ubuntu 18.10 Status in linux package in Ubuntu: Confirmed Bug description: When I upgraded to Ubuntu 18.10 from Ubuntu 18.04, the SD card reader on my Macbook pro early 2015 13 inch stopped working. It won't show up when I do lspci. The SD card reader won't show up in gparted or gnome- disk-utility. My Kernel version is 4.18.0-10-generic Output of lspci 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 09) 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) 00:15.0 DMA controller: Intel Corporation Wildcat Point-LP Serial IO DMA Controller (rev 03) 00:15.4 Serial bus controller [0c80]: Intel Corporation Wildcat Point-LP Serial IO GSPI Controller #1 (rev 03) 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) 00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #2 (rev e3) 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) 00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #5 (rev e3) 00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #6 (rev e3) 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) 00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03) 02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime HD Camera 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC (rev 01) 04:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01) 05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] 07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI [Falcon Ridge 4C 2013] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: monter 1583 F pulseaudio /dev/snd/controlC0: monter 1583 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/17/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 180.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr180.0.0.0.0:bd09/17/2018:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To
[Kernel-packages] [Bug 1802646] Re: no shutdown, reboot, suspent because i changed cpu from tf 20 to turion 68 (Aspire 5516)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802646 Title: no shutdown,reboot,suspent because i changed cpu from tf 20 to turion 68 (Aspire 5516) Status in linux package in Ubuntu: Confirmed Bug description: nothing is crashing its just doesn't shutdown reboot or sleep(wakes up 1 second after it sleeps) for the day a change cpu from AMD Athlon 64 TF-20 to AMD Turion 64 X2 TL-68 for the Acer Aspire 5516 and 18.10 lubuntu cant install from usb live cdrom/casper/filesystem.squashfs error something for Acer Aspire 5516 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-38-generic. AplayDevices: List of PLAYBACK Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acer845 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf040 irq 16' Mixer name : 'Realtek ALC272X' Components : 'HDA:10ec0272,10250213,0011' Controls : 21 Simple ctrls : 10 CurrentDesktop: LXDE Date: Sat Nov 10 15:32:05 2018 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5516 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f16d84dc-e5a8-481f-8baa-2f06e289b595 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.10 dmi.board.name: Aspire 5516 dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.10:bd04/21/2009:svnAcer:pnAspire5516:pvrV1.10:rvnAcer:rnAspire5516:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5516 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802077] Re: Bluetooth is not working on Lenovo IdeaPad Y560p
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802077 Title: Bluetooth is not working on Lenovo IdeaPad Y560p Status in linux package in Ubuntu: Confirmed Bug description: No bluetooth device is found. `rfkill list` shows a wifi device only, no bluetooth. # rfkill list 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Nov 7 12:07:34 2018 HibernationDevice: RESUME=/dev/mapper/vg-swap MachineType: LENOVO IdeaPad Y560p ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=/dev/mapper/vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-14 (176 days ago) dmi.bios.date: 11/12/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 3FCN11WW dmi.board.name: KL3 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr3FCN11WW:bd11/12/2010:svnLENOVO:pnIdeaPadY560p:pvrRev1.0:rvnLENOVO:rnKL3:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0: dmi.product.name: IdeaPad Y560p dmi.product.version: Rev 1.0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Screen flickers when using radeon.ko. It's a regression, it didn't happen on Trusty. [Fix] Quote the original commit log: "Instead of the closest reference divider prefer the lowest". [Test] Affected user confirms it fixes the issue. [Regression Potential] Low. Only affect radeaon, and it's in upstream stable tree. === Original Bug Report === my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775165 Title: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1775165 [Impact] When userspace tasks which are processing fanotify permission events act incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes the whole notification subsystem to hang. This has been seen in production, and it can also be seen when running the Linux Test Project testsuite, specifically fanotify07. [Fix] Instead of holding the SRCU lock while waiting for userspace to respond, which may never happen, or not in the order we are expecting, we drop the fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then reacquire the lock again when userspace responds. The fixes are from a series of upstream commits: 05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick) 9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport) abc77577a669f424c5d0c185b9994f2621c52aa4 (backport) The following are upstream commits necessary for the fixes to function: 35e481761cdc688dbee0ef552a13f49af8eba6cc (backport) 0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick) [Testcase] You can reproduce the problem pretty quickly with the Linux Test Project: Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs 9. ./runltp -f /tmp/jobs On a stock Xenial kernel, the system will hang, and the testcase will look like: <<>> tag=fanotify07 stime=1554326200 cmdline="fanotify07 " contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> Looking at dmesg, we see the following call stack [ 790.772792] LTP: starting fanotify07 (fanotify07 ) [ 960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds. [ 960.140867] Not tainted 4.4.0-142-generic #168-Ubuntu [ 960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 960.141498] fsnotify_mark D 8800b6703c98 036 2 0x [ 960.141516] 8800b6703c98 88013a558a00 8800b7797000 8800b66f8000 [ 960.141524] 8800b6704000 7fff 8800b6703de0 8800b66f8000 [ 960.141528] 8800b6703cb0 8185cb45 8800b6703de8 [ 960.141532] Call Trace: [ 960.141580] [] schedule+0x35/0x80 [ 960.141588] [] schedule_timeout+0x1b4/0x270 [ 960.141617] [] ? mod_timer+0x10c/0x240 [ 960.141621] [] ? __schedule+0x30d/0x810 [ 960.141625] [] wait_for_completion+0xb2/0x190 [ 960.141636] [] ? wake_up_q+0x70/0x70 [ 960.141641] [] __synchronize_srcu+0x100/0x1a0 [ 960.141645] [] ? trace_raw_output_rcu_utilization+0x60/0x60 [ 960.141664] [] ? fsnotify_put_mark+0x40/0x40 [ 960.141669] [] synchronize_srcu+0x24/0x30 [ 960.141672] [] fsnotify_mark_destroy+0x84/0x130 [ 960.141680] [] ? wake_atomic_t_function+0x60/0x60 [ 960.141691] [] kthread+0xe7/0x100 [ 960.141694] [] ? __schedule+0x301/0x810 [ 960.141699] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 960.141703] [] ret_from_fork+0x55/0x80 [ 960.141706] [] ? kthread_create_on_node+0x1e0/0x1e0 The vanilla 4.4 kernel also shows the same call stack. On a patched kernel, the test will pass successfully, and there will be no messages in dmesg. [Regression Potential] This makes modifications to how locking is performed in fsnotify / fanotify and there may be some cause for regression. Running all fanotify Linux Test Project tests shows that there are no extra failures caused by the patches, and instead fewer failures are seen due to the bugfix. Running the entire Linux Test Project testsuite
[Kernel-packages] [Bug 1802052] Re: WMI Error - ACPI Exception AE_NOT_FOUND
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802052 Title: WMI Error - ACPI Exception AE_NOT_FOUND Status in linux package in Ubuntu: Confirmed Bug description: Backstory: The discrete touchpad enable/disable switch does not work on Ubuntu but works perfectly on windows. This is probably an issue of the msi_wmi drivers, so I tried to find a solution. Followed the instructions here - https://wiki.ubuntu.com/Kernel/Reference/WMI WMI dump error - AE_NOT_FOUND Logs - https://pastebin.com/aY6ngxzh ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pratyush 4060 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 7 12:02:12 2018 InstallationDate: Installed on 2018-09-17 (50 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803268] Re: Xubuntu 18.10 after Blank Screen, System Will NOT Unblank
*** This bug is a duplicate of bug 1801609 *** https://bugs.launchpad.net/bugs/1801609 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803268 Title: Xubuntu 18.10 after Blank Screen, System Will NOT Unblank Status in linux package in Ubuntu: Confirmed Bug description: Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Toshiba's Screen has Blanked, it will not unblank with normal Keystrokes or Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will then unblank the Toshiba's Screen!!! version.log Ubuntu 4.18.0-10.11-generic 4.18.12 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: houston2335 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 13 22:42:09 2018 InstallationDate: Installed on 2018-11-01 (12 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: TOSHIBA Satellite C650 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=9d27207e-4cea-4a3f-9e73-35d175aa6a19 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd11/21/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-07J001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C650 dmi.product.sku: PSC2EC-07J001 dmi.product.version: PSC2EC-07J001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803474] Re: ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq Presario 21-N1F3AR
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803474 Title: ELANTECH touchpad detected as PS/2 Logitech Wheel Mouse on Compaq Presario 21-N1F3AR Status in linux package in Ubuntu: Confirmed Bug description: Hello, I formerly had installed Ubuntu 18.04 with the same problem, my touchpad was detected as a generic PS2 mouse so I thought that if I upgraded my Ubuntu version (currently 18.10) my problem would be solved. I tried several fixes that I found on different forums with my previous version but they didn't work. I'm not an advanced user and I was looking forward to finally switch to linux but this is a big problem for me. I attached some files except cat /var/log/Xorg.0.log > Xorg.0.log cat: /var/log/Xorg.0.log: No existe el archivo o el directorio (missing file or directory) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flor 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 14 22:27:10 2018 InstallationDate: Installed on 2018-11-10 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 058f:3822 Alcor Micro Corp. Bus 001 Device 002: ID 8087:07dc Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: COMPAQ Presario 21 VerK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=39b22cde-4b65-4213-8812-e830a36afe55 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-14 (0 days ago) dmi.bios.date: 02/27/2016 dmi.bios.vendor: COMPAQ dmi.bios.version: fd dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: K21 dmi.board.vendor: EA dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnCOMPAQ:bvrfd:bd02/27/2016:svnCOMPAQ:pnPresario21VerK:pvrTBDbyOEM:rvnEA:rnK21:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Presario 21 VerK dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: COMPAQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802076] Re: Trackpad not detected
*** This bug is a duplicate of bug 1781879 *** https://bugs.launchpad.net/bugs/1781879 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802076 Title: Trackpad not detected Status in linux package in Ubuntu: Incomplete Bug description: My Laptop is an ASUS TUF FX504 Series model. I installed ubuntu 18.04.1 on it but my trackpad is not detected. Attaching an external mouse works fine. Trackpad is easily identified by Windows 10. `cat /proc/bus/input/devices | grep Name` shows the output: ``` N: Name="Sleep Button" N: Name="Power Button" N: Name="Lid Switch" N: Name="Power Button" N: Name="AT Translated Set 2 keyboard" N: Name="Video Bus" N: Name="Video Bus" N: Name="Asus Wireless Radio Control" N: Name="Asus WMI hotkeys" N: Name="USB2.0 HD UVC WebCam: USB2.0 HD" N: Name="HDA Intel PCH Front Headphone" N: Name="HDA Intel PCH HDMI/DP,pcm=3" N: Name="HDA Intel PCH HDMI/DP,pcm=7" N: Name="HDA Intel PCH HDMI/DP,pcm=8" N: Name="HDA Intel PCH HDMI/DP,pcm=9" N: Name="HDA Intel PCH HDMI/DP,pcm=10" N: Name="E-Signal USB Gaming Mouse" N: Name="E-Signal USB Gaming Mouse" ``` I have also attached the output of `cat /proc/bus/input/devices > ~/devices` to this post. `uname -a` outputs: > Linux ayush-TUF-GAMING-FX504GM-FX80GM 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Regards Ayush To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801739] Re: Disco update: v4.19.1 upstream stable release
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801739 Title: Disco update: v4.19.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.19.1 upstream stable release from git://git.kernel.org/ The following patches from the v4.18.7 stable release shall be applied: bridge: do not add port to router list when receives query with source 0.0.0.0 ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called net/mlx5e: fix csum adjustments caused by RXFCS net: sched: gred: pass the right attribute to gred_change_table_def() net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules net: udp: fix handling of CHECKSUM_COMPLETE packets Revert "net: simplify sock_poll_wait" rtnetlink: Disallow FDB configuration for non-Ethernet device vhost: Fix Spectre V1 vulnerability bonding: fix length of actor system openvswitch: Fix push/pop ethernet validation net/ipv6: Allow onlink routes to have a device mismatch if it is the default route net/smc: fix smc_buf_unuse to use the lgr pointer mlxsw: spectrum_switchdev: Don't ignore deletions of learned MACs mlxsw: core: Fix devlink unregister flow net: drop skb on failure in ip_check_defrag() net: Properly unlink GRO packets on overflow. r8169: fix broken Wake-on-LAN from S5 (poweroff) Revert "be2net: remove desc field from be_eq_obj" sctp: check policy more carefully when getting pr status sparc64: Export __node_distance. sparc64: Make corrupted user stacks more debuggable. sparc64: Wire up compat getpeername and getsockname. net: bridge: remove ipv6 zero address check in mcast queries Linux 4.19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789146] Re: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789146 Title: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: On Mon, Apr 16, 2018 at 8:20 AM, Czurylo, Krzysztof wrote: > > I suspect the problem is caused by a bug in the kernel. > > I did a few experiments and it looks like the issue occurs only if the > filesystem is mounted with "-o dax". I can reproduce is both for xfs > and ext4, so it's not FS-specific, but rather DAX-specific. It also > reproduces on an emulated PMEM - no need to use real AEP DIMMs. > > Using the latest kernel (4.16.0) does not help. > > What happens: > > In debug version of libpmemlog (but also libpmemblk), the entire pool > is by default write-protected with mprotect(..., PROT_READ). > > When the program attempts to write some data to the pool (i.e. > pmemlog_append, pmemblk_write, ...), the library unprotects the pages > to be modified (usually just one or two pages) and once the data is > stored, the pages are protected again. > > Inside the kernel, mprotect splits the memory region associated with > the pool into 3 regions: the read-only head and tail + one r/w page in > the middle. > > The problem is that after the last step, the memory region associated > with the modified page is not merged with the adjacent regions having > the same protection flags (ro) to form one big read-only region again. > This leads to the situation where we have thousands of 4K memory > mappings per process that are tracked by the kernel separately. When > the number of maps exceeds the limit (default is 65536 - see: > /proc/sys/vm/max_map_count), mprotect fails with ENOMEM, which aborts > the program. Commitid: e1fb4a0864958fac2fb1b23f9f4562a9f90e3e8f dax: remove VM_MIXEDMAP for fsdax and device dax Target Kernel: 4.19 Target Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1789146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798165
Title:
Vulkan applications cause permanent memory leak with Intel GPU
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
memory is never freed and can cause a system crash if the applications are
used for long enough. Certain applications can make the leak be as high as
10 MB/minute.
This commit has been cc'd to upstream stable, but it has not landed in
Bionic or Cosmic as of yet.
Details about the upstream bug can be seen at:
https://github.com/doitsujin/dxvk/issues/632
https://bugs.freedesktop.org/show_bug.cgi?id=107899
== Fix ==
337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")
== Regression Potential ==
Low. This commit has been cc'd to stable, so it has had additional
upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Vulkan applications, as Dota 2 and DXVK games cause a memory leak
where memory is never freed and can cause a system crash if the
applications are used for long enough. Certain applications can make
the leak be as high as 10 MB/minute.
Details about this bug can be seen at
https://github.com/doitsujin/dxvk/issues/632 and
https://bugs.freedesktop.org/show_bug.cgi?id=107899
This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
The particular commit is:
commit a2cef7d049f07995406b403605119a54881daf15
Author: Jason Ekstrand
Date: Wed Sep 26 02:17:03 2018 -0500
drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set
commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.
We attempt to get fences earlier in the hopes that everything will
already have fences and no callbacks will be needed. If we do succeed
in getting a fence, getting one a second time will result in a duplicate
ref with no unref. This is causing memory leaks in Vulkan applications
that create a lot of fences; playing for a few hours can, apparently,
bring down the system.
Cc: sta...@vger.kernel.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
Reviewed-by: Chris Wilson
Signed-off-by: Jason Ekstrand
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
Signed-off-by: Greg Kroah-Hartman
On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
https://i.imgur.com/qMAvuwl.png
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: usuario4655 F pulseaudio
/dev/snd/seq:usuario4640 F timidity
CurrentDesktop: XFCE
Date: Tue Oct 16 14:16:54 2018
HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
InstallationDate: Installed on 2017-06-13 (489 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt
i915.enable_gvt=1 i915.fastboot=1
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-36-generic N/A
linux-backports-modules-4.15.0-36-generic N/A
linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias:
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
[Kernel-packages] [Bug 1789638] Re: azure 4.15 kernel: reading sysfs file causing oops
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1789638 Title: azure 4.15 kernel: reading sysfs file causing oops Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Fix Released Bug description: Kernel: 4.15.0-1021-azure, in Xenial VM on Azure. How to reproduce: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make ./stress-ng --sysfs 0 -t 120 One gets the following: [ 22.451885] BUG: unable to handle kernel NULL pointer dereference at 0004 [ 22.455286] IP: read_avail_show+0x1c/0x40 [ 22.455286] PGD 80042d59e067 P4D 80042d59e067 PUD 42eb8c067 PMD 0 [ 22.455286] Oops: [#1] SMP PTI [ 22.455286] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables serio_raw joydev hv_balloon ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb hid_hyperv pata_acpi cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils [ 22.455286] CPU: 1 PID: 1670 Comm: cat Not tainted 4.15.0-1021-azure #21~16.04.1-Ubuntu [ 22.455286] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 22.455286] RIP: 0010:read_avail_show+0x1c/0x40 [ 22.455286] RSP: 0018:afa4c4eafdb0 EFLAGS: 00010286 [ 22.455286] RAX: RBX: 9db36c93e880 RCX: 9db36f136908 [ 22.860062] RDX: RSI: 9db364548000 RDI: 9db364548000 [ 22.888042] RBP: afa4c4eafdb0 R08: 9db364548000 R09: 9db36c049840 [ 22.920041] R10: 9db364548000 R11: R12: 92ae9440 [ 22.948058] R13: 9db36c22d200 R14: 0001 R15: 9db36c93e880 [ 22.972043] FS: 7f67eeec6700() GS:9db37fd0() knlGS: [ 23.004046] CS: 0010 DS: ES: CR0: 80050033 [ 23.024016] CR2: 0004 CR3: 00042c37a003 CR4: 001606e0 [ 23.048014] Call Trace: [ 23.060019] vmbus_chan_attr_show+0x21/0x30 [ 23.076018] sysfs_kf_seq_show+0xa2/0x130 [ 23.088030] kernfs_seq_show+0x27/0x30 [ 23.100020] seq_read+0xb7/0x480 [ 23.112014] kernfs_fop_read+0x111/0x190 [ 23.128017] ? security_file_permission+0xa1/0xc0 [ 23.144013] __vfs_read+0x1b/0x40 [ 23.156019] vfs_read+0x93/0x130 [ 23.168013] SyS_read+0x55/0xc0 [ 23.180021] do_syscall_64+0x73/0x130 [ 23.192014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 23.212022] RIP: 0033:0x7f67ee9d8260 [ 23.224016] RSP: 002b:7fffdc193ff8 EFLAGS: 0246 ORIG_RAX: [ 23.252022] RAX: ffda RBX: 0002 RCX: 7f67ee9d8260 [ 23.276019] RDX: 0002 RSI: 7f67eed0c000 RDI: 0003 [ 23.300020] RBP: 0002 R08: R09: [ 23.328025] R10: 037b R11: 0246 R12: 7f67eed0c000 [ 23.352036] R13: 0003 R14: R15: 0002 [ 23.376678] Code: fb 3a 17 00 48 98 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 8b 87 38 01 00 00 49 89 f0 8b 97 48 01 00 00 4c 89 c7 48 89 e5 <8b> 48 04 8b 00 29 ca 89 c6 29 ce 01 c2 39 c1 0f 46 d6 48 c7 c6 [ 23.444022] RIP: read_avail_show+0x1c/0x40 RSP: afa4c4eafdb0 [ 23.468021] CR2: 0004 [ 23.481135] ---[ end trace 348a4b7d5a6747d1 ]--- Cornered this down to just reading: cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/99221fa0 -24ad-11e2-be98-001aa01bbf6e/channels/4/read_avail There are various /sysfs VMBUS files that trigger this, see a fix on comment #5 below that addresses all the ones I could find. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789333] Re: linux-image-4.15.0-33-generic breaks WiFi
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789333
Title:
linux-image-4.15.0-33-generic breaks WiFi
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since the upgrade from linux-image-4.15.0-32-generic to linux-
image-4.15.0-33-generic my Dell XPS 13 L322X laptop is unable to
connect to my home WiFi network. It is unable to obtain an IP through
DHCP but more in general it seems unable to receive packets. If I set
up an IP address manually I still cannot ping my router. There are no
noteworthy messages coming through dmesg though. The laptop uses an
AR9462 Wireless Network Adapter and not all WiFi networks fail to work
(but my home network fails to connect in a reproducible manner). The
following step were used to diagnose the problem:
$ uname -a
Linux apol1 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=60 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-33 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:48 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85:56ff:fe8f:45f5 prefixlen 64 scopeid 0x20
ether bc:85:56:8f:45:f5 txqueuelen 1000 (Ethernet)
RX packets 49 bytes 9692 (9.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 68 bytes 15466 (15.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ sudo dhclient -v wlp1s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on Socket/fallback
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x247b5867)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 3 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 4 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 7 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 18 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 20 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 17 (xid=0x16dac52f)
DHCPDISCOVER on wlp1s0 to 255.255.255.255 port 67 interval 15 (xid=0x16dac52f)
...
The dhclient command never succeeds. If I revert to kernel linux-
image-4.15.0-32-generic everything works fine instead:
$ uname -a
Linux apol1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ sudo /etc/init.d/network-manager stop
$ echo -e "network={\nssid=\"HT_B23514\"\npsk=\"\"\n}"
> /tmp/wpa_supplicant.conf
$ sudo wpa_supplicant -B -iwlp1s0 -c/tmp/wpa_supplicant.conf -Dwext
$ iwconfig wlp1s0
wlp1s0IEEE 802.11 ESSID:"HT_B23514"
Mode:Managed Frequency:2.412 GHz Access Point: 00:16:FB:B2:35:14
Bit Rate=144.4 Mb/s Tx-Power=19 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-24 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:12 Missed beacon:0
$ ifconfig wlp1s0
wlp1s0: flags=4163 mtu 1500
inet6 fe80::be85:56ff:fe8f:45f5 prefixlen 64 scopeid 0x20
ether bc:85:56:8f:45:f5 txqueuelen 1000 (Ethernet)
RX packets 586 bytes 364645 (364.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 684 bytes 191764 (191.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
$ sudo dhclient -v wlp1s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on LPF/wlp1s0/bc:85:56:8f:45:f5
Sending on Socket/fallback
DHCPREQUEST of 10.10.10.2 on wlp1s0 to 255.255.255.255 port 67
(xid=0x518398de)
[Kernel-packages] [Bug 1789519] Re: Low Memory corruption logged in syslog
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789519 Title: Low Memory corruption logged in syslog Status in linux package in Ubuntu: Confirmed Bug description: Dell Inspiron 3847 Desktop running Ubuntu 18.04.1 LTS kernel: 4.15.0-33-generic Corrupted low memory messages logged in syslog Can be reproduced with script: #!/bin/bash # log to syslog... logger -st low_mem_corruption.sh "Checking for low memory corruption with kernel $(uname -rv)..." # this will cause syslog messages on affected kernels... cat /proc/i8k logger -st low_mem_corruption.sh "Please wait for 90 secs to ensure low memory test has completed..." # sleep for 1.5 mins - enough time for mem check every 60 secs... sleep 90 logger -st low_mem_corruption.sh "Check for low memory corruption done! Was anything logged in syslog?" Kernels tested: Kernel 4.15.0-29-generic - fine Kernel 4.15.0-30-generic - fine Kernel 4.15.0-30-generic - Never installed, do not know - did it exist? Kernel 4.15.0-32-generic - Low Memory corruption! Kernel 4.15.0-33-generic - Low Memory corruption! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bossman1316 F pulseaudio /dev/snd/pcmC1D0p: bossman1316 F...m pulseaudio /dev/snd/controlC1: bossman1316 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 28 16:56:01 2018 HibernationDevice: RESUME=UUID=1c065a24-2acf-43dc-bf3d-1382f3bbf0ac InstallationDate: Installed on 2018-05-12 (108 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3847 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=a5dec663-366e-4ecc-a17a-ce4219c54897 ro quiet loglevel=3 splash RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/10/2018:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799180] Re: Ubuntu 18.10 / Linux 4.19 -rc7/8/Final - System slows / stops
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799180 Title: Ubuntu 18.10 / Linux 4.19 -rc7/8/Final - System slows / stops Status in linux package in Ubuntu: Confirmed Bug description: Hi there folks sorry if it's inappropriate to report a bug in an upstream release candidate kernel, but as a suggested test / fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743 I was told to install an upstream kernel, which I did. When I run with that kernel for any length of time, or do anything involving high CPU (like run Firefox for instance) the system fan begins to whine and the system slows down to the point where it finally hangs. I tried to run 'ubuntu-bug linux' from the terminal, but when I do I get the error seen in the screenshot (attached). I'll go back to running 4.18 for now because not being able to sleep the laptop isn't a show stopper, but it's definitely something I consider important for a fully fledged operating system / work environment :) Thanks and please let me know if there's anything I can do to provide more data / help with testing / etc. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-07 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802821] Re: Serious design flaw using large external drives.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802821 Title: Serious design flaw using large external drives. Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Bug description: I am trying to recover data from an HFS+ files system on a 4TB external USB 3 drive. Copying 3TB from the 4TB HFS+ drive to a 4TB NTFS drive using MATE Terminal cp -anR from to took 2 days. When I try to copy the same data to a 6TB NTFS USB 3 drive the results are glacial. 750GB has taken over 6 days. Obviously there is a problem of scale drive in Ubuntu MATE. I invite the developers to plug in a 12TB drive and see just how glacial (no - not glacial, more on the order of plate techtonics) slow their design is. Robert Pearson ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2102 F pulseaudio /dev/snd/controlC0: robert 2102 F pulseaudio CurrentDesktop: MATE Date: Sun Nov 11 23:50:13 2018 HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb InstallationDate: Installed on 2018-10-25 (18 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1802821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789459] Re: linux: 4.18.0-7.8 -proposed tracker
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789459 Title: linux: 4.18.0-7.8 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: This bug is for tracking the 4.18.0-7.8 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1789459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802834] Re: Dim screen after first boot on Thinkpad A285
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802834 Title: Dim screen after first boot on Thinkpad A285 Status in linux package in Ubuntu: Confirmed Bug description: We installed the 18.04 daily image on ThinkPad A285, found the screen is dim at the first boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1481 F pulseaudio /dev/snd/controlC0: u 1481 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20MWZ47RUS Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=347498ab-8eae-42d3-a1e3-74e9be6b6ba3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0XET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MWZ47RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0XET30W(1.07):bd09/21/2018:svnLENOVO:pn20MWZ47RUS:pvrThinkPadA285:rvnLENOVO:rn20MWZ47RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad A285 dmi.product.name: 20MWZ47RUS dmi.product.version: ThinkPad A285 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809630] Re: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809630 Title: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Bug description: There are 7 test cases failed in secomp_bpf test, and this can be reproduced with test suites from the upstream: [ RUN ] TRACE_syscall.ptrace_syscall_dropped TRACE_syscall.ptrace_syscall_dropped: Test failed at step #159 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped [ RUN ] TRACE_syscall.syscall_dropped TRACE_syscall.syscall_dropped: Test failed at step #2 [ FAIL ] TRACE_syscall.syscall_dropped [ RUN ] TRACE_syscall.skip_after_RET_TRACE seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ RUN ] TRACE_syscall.kill_after_RET_TRACE TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ RUN ] TRACE_syscall.skip_after_ptrace seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [ FAIL ] TRACE_syscall.skip_after_ptrace [ RUN ] TRACE_syscall.kill_after_ptrace TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_ptrace [ RUN ] global.get_metadata seccomp_bpf.c:2913:global.get_metadata:Expected sizeof(md) (16) == ptrace(0x420d, pid, sizeof(md), ) (18446744073709551615) global.get_metadata: Test terminated by assertion [ FAIL ] global.get_metadata Please find the complete test report here: https://pastebin.ubuntu.com/p/tfmVypShtX/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic s390x NonfreeKernelModules: zfs zunicode zavl icp 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': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Dec 24 03:33:04 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802665] Re: No Restart Shutdown or Suspend (Aspire 5516)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802665 Title: No Restart Shutdown or Suspend (Aspire 5516) Status in linux package in Ubuntu: Confirmed Bug description: Reason is i changed cpu from tf 20 to turion 64 tl 68 for acer aspire 5516 plus when i try to install 18.10 from usb it fails and displays cdrom/casper/filesystem.squashfs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acer 1847 F pulseaudio CurrentDesktop: LXQt Date: Sat Nov 10 12:41:18 2018 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer Aspire 5516 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=435bbf22-b287-40fd-ae42-298df9db9a13 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-09 (0 days ago) dmi.bios.date: 04/21/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.10 dmi.board.name: Aspire 5516 dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV1.10:bd04/21/2009:svnAcer:pnAspire5516:pvrV1.10:rvnAcer:rnAspire5516:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5516 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800118] Re: NVHDA does not persist after Suspend or Hibernating
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800118 Title: NVHDA does not persist after Suspend or Hibernating Status in linux package in Ubuntu: Incomplete Bug description: Below is a Cut and paste of a recent Ubuntu Forum Page where I posted the issues https://ubuntuforums.org/showthread.php?t=2404566 Note that though it says "Solved" it is just workarounds of Bigger ACPI Issues! ubuntu 18.10 OK, This is a new thread, and I will make it HUGE! Edit Solution/ Work Around for the "2/" Problem see Post # 4, Thanks PeterSaints Ubuntu, Please Listen! Nvidia, HDA WOES in the Title ... HDA stands for High Definition Audio, or HDMI Audio, or Surround Sound 5.1-7.1 etc. ... NVHDA stands for Nvidia HDA. Just for anyone who does not know the Jargon! What does Work ... (and I will post ALL my Notes and Links for others below!) 1/ Everything AFTER STUPIDLY!, I need to install a Kernel PATCH! and 2/ A STUPIDLY Necessary Restart after ANY Hibernation or Suspend! First my System, and most importantly is it is a NEW Cutting Edge Hp Omen X Laptop with a Nvidia GTX 1080m GPU, and the latest Linux 3.18 Kernel! -Computer- Processor : Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz Memory: 16245MB (3330MB used) Machine Type : Notebook Operating System : Ubuntu 18.10 -Display- Resolution: 1920x1080 pixels OpenGL Renderer : GeForce GTX 1080/PCIe/SSE2 X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel PCH Audio Adapter : HDA-Intel - HDA NVidia -Input Devices- Video Bus ST LIS3LV02DL Accelerometer HDA Intel PCH Mic HDA Intel PCH Mic HDA Intel PCH Headphone HP WMI hotkeys HDA NVidia HDMI/DP,pcm:3 HDA NVidia HDMI/DP,pcm:7 HDA NVidia HDMI/DP,pcm:8 So the LATEST 2 Problems I am looking for a SOLUTION that would indeed help THOUSANDS and/or MILLIONS of people Now and/or in the near future! 1/ Why SHOULD I need to apply a PATCH to a YEAR old KNOWN problem! and MORE IMPORTANTLY! 2/ Why is the fixed Patch System NOT working after a Suspend or Hibernation (Yes I am reiterating my issue once again!) After EITHER a Suspend or Hibernation, the HDA Sound is EITHER, 1/ Not VISIBLE AGAIN! ANYWHERE! Trust me, or 2/ Visible but in a Dysfunctional State, ... Showing 3 version of the NVHDA 0,1&2 ... and NONE of the 3 (three) WORK! to be clear NO SOUND AT ALL! when testing them. So I will leave it here, and to show my continued Good Faith and Obvious Continued Support For Ubuntu, below are ALL my Solutions to Date! 1st Solution - Install the patch to get the INVISIBLE and/or Unloaded HDA Visible and/or Loaded ∘ I can confirm that kernel module, posted by ‣ Maik Freudenberg (https://bugs.freedesktop.org/show_bug.cgi?id=75985#c27), • Kernel module to toggle audio function ∘ is working fine on my system. Thank you for the fix. The HDMI audio device now works as it should (now detected). ∘ The steps I did to enable HDMI audio device: • 1. Download and extract the file nvhda.tar.xz. (from above link) • 2. Run these commands in Terminal, in the location of the extracted folder Code: • $ make • $ sudo make install • $ echo nvhda | sudo tee -a /etc/initramfs-tools/modules • $ echo "options nvhda load_state=1" | sudo tee /etc/modprobe.d/nvhda.conf • $ sudo update-initramfs -u ‣ 3. Reboot. ## SOLVED ## ### 2nd Solution Hibernation/Suspend Working (Not HDA Sound of Course) Troubleshooting ‣ Prerequisites - does your kernel support suspend-to-disk? • Kernel supports whatever is listed in /sys/power/state, so: Code: cat /sys/power/state ∘ Allowed (to my knowledge) entries there include: mem, standby, freeze, disk. Explanation: ‣ mem - has several meanings, which one exactly on your system you'll find out via cat /sys/power/mem_sleep. I have: s2idle [deep] ‣ standby - Power-On Suspend (if supported) ‣ freeze - Suspend To Idle (STI) ‣ disk - Hibernate - Suspend To Disk (STD), This - you want. ∘ mine says : freeze mem disk - PERFECT! • Then we need to check Code: $ cat /sys/power/disk ‣ If (good) shows ... ‣ [platform] shutdown reboot suspend test_resume • if : (Bad) • [disabled] • (not very good) ‣ Enable Hibernate and put it in menu - Easy-Peasy • Software Prerequisites Code: sudo apt install pm-utils cpufrequtils 1. Edit a specific file with this command. Code: sudo gedit /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla ∘ 2. Scroll down the Text Document and find the below sections: [Disable hibernate by default in upower] [Disable hibernate by default in logind] ‣ Change both the values from no to yes in: ResultActive=no (change this to yes)
[Kernel-packages] [Bug 1789436] Re: pmtu.sh fails on 4.18 kernel
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789436 Title: pmtu.sh fails on 4.18 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: pmtu.sh is a network selftest that was introduced on 4.17. It is currently failing on 4.18. After revert of ccd740cbc6 "vti6: Add pmtu handling to vti6_xmit.", it passes. The fail is in the nature of holding netdevices refcounts, so some network operations start hanging, including the loading and removal of network modules. [ 159.936543] unregister_netdevice: waiting for veth_b to become free. Usage count = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789135] Re: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789135 Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Now unable to restart current applications on the host. Serious problem. root@xray:/boot# su zimbra zimbra@xray:/boot$ zmcontrol start Perl API version v5.14.0 of Socket does not match v5.18.0 at /usr/share/perl/5.18/XSLoader.pm line 117. Compilation failed in require at /usr/lib/perl/5.18/Sys/Syslog.pm line 10. BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Sys/Syslog.pm line 10. Compilation failed in require at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23. BEGIN failed--compilation aborted at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 23. Compilation failed in require at /opt/zimbra/bin/zmcontrol line 27. BEGIN failed--compilation aborted at /opt/zimbra/bin/zmcontrol line 27. zimbra@xray:/boot$ ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 NonfreeKernelModules: gpio_ich lpc_ich hpilo mac_hid e752x_edac edac_core shpchp tg3 cciss pata_acpi AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 26 19:29 seq crw-rw 1 root audio 116, 33 Aug 26 19:29 timer AplayDevices: aplay: device_list:268: no soundcards found... ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: arecord: device_list:268: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sun Aug 26 20:36:34 2018 DuplicateSignature: package:linux-image-3.13.0-45-generic:3.13.0-45.74:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=01d95e3f-884b-481d-b871-b941923121e2 InstallationDate: Installed on 2011-04-13 (2692 days ago) InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1) IwConfig: eth2 no wireless extensions. eth3 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP ProLiant DL380 G4 PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-117-generic root=/dev/mapper/hostname-root ro text RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux Title: package linux-image-3.13.0-45-generic 3.13.0-45.74 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2018-08-26 (0 days ago) dmi.bios.date: 07/19/2007 dmi.bios.vendor: HP dmi.bios.version: P51 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP51:bd07/19/2007:svnHP:pnProLiantDL380G4:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789314] Re: linux 4.17.0-9.10 ADT test failure with linux 4.17.0-9.10
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789314 Title: linux 4.17.0-9.10 ADT test failure with linux 4.17.0-9.10 Status in linux package in Ubuntu: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/i386/l/linux/20180827_192751_f3195@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802738] Re: cdc_acm driver lacks trival support for Hiro (Conexant) H05228 USB modem
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802738 Title: cdc_acm driver lacks trival support for Hiro (Conexant) H05228 USB modem Status in linux package in Ubuntu: Fix Released Bug description: I procured a USB modem manufactured by Hiro (model number H50228). This is in fact a Conexant modem, and while some conexant models are supported in cdc_adm, this particular type is not. Hence, when I connect the modem to my system, cdc_adm does not initialize the modem properly, as evidenced by errors reported through journalctl: Nov 10 21:46:10 kernel: usbcore: registered new interface driver cdc_acm Nov 10 21:46:10 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Nov 10 21:47:01 kernel: cdc_acm 4-2:1.0: Zero length descriptor references Nov 10 21:47:01 kernel: cdc_acm: probe of 4-2:1.0 failed with error -22 Similar errors of this type have been reported previously, and following the resolution for these errors I recompiled the cdc_acm kernel module, after which the modem is successfully registered: Nov 10 21:47:48 kernel: usbcore: registered new interface driver cdc_acm Nov 10 21:47:48 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Nov 10 21:48:17 kernel: cdc_acm 4-2:1.0: ttyACM0: USB ACM device With my modified kernel module, the modem works (at least for the purposes I need it). I will attach the patch once this bug has been opened. I don't know how to submit a patch for formal consideration so need some help on that front... Neither am I sure how to figure out exactly if this was already addressed in an upstream fix. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacobsma 4053 F pulseaudio /dev/snd/controlC0: jacobsma 4053 F pulseaudio /dev/snd/controlC2: jacobsma 4053 F pulseaudio CurrentDesktop: XFCE Date: Sun Nov 11 11:20:40 2018 HibernationDevice: RESUME=UUID=899fa33b-30cb-41f4-b709-557ad528a5bd InstallationDate: Installed on 2016-03-06 (979 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=70a8bdf6-e697-4112-b584-4b650002555d ro RelatedPackageVersions: linux-restricted-modules-4.4.0-138-generic N/A linux-backports-modules-4.4.0-138-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2018-03-16 (240 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802578] Re: [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22
** Tags added: ubuntu-certified ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802578 Title: [drm:intel_display_resume [i915]] *ERROR* Restoring old state failed with -22 Status in linux package in Ubuntu: Confirmed Bug description: This error appears in my journal quite often after resuming laptop from suspend and when un-docking the machine in the meantime. When docked, I usually only enable two external displays. Un-docked I only have the built-in display on the laptop. This was working flawlessly in 18.04 but is extremely buggy now after having upgraded to 18.10 for some reason. When this happens, my screen(s) remain pitch black. Switching to TTYs and back does not help. CTRL+ALT+F1 gives me the GDM login, but when entering password it seems it switches to TTY2 (or whatever is at CTRL+ALT+F2), and the screen(s) remain black. Logging in in a TTY and trying to "DISPLAY=:0.0 gnome-shell --replace" does not help. +P does not work (is this shortcut combination removed?). At last when I ran "xrandr --auto" the session I had crashed and I had to re-login, but at least this time I got my desktop. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexander 23057 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 20:34:53 2018 HibernationDevice: RESUME=/swapfile InstallationDate: Installed on 2018-05-02 (190 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HN0013MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash net.ifnames=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-01 (7 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET55W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0013MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET55W(1.33):bd09/14/2018:svnLENOVO:pn20HN0013MX:pvrThinkPadX270:rvnLENOVO:rn20HN0013MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0013MX dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802652] Re: keyboard backlight not working on Asus GM501
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 Status in linux package in Ubuntu: Confirmed Bug description: The keyboard lights and most of the F keys aren't working. Kernel = 4.15.0-20-generic System linux mint 19 ls -hal /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 10 15:47 . drwxr-xr-x 72 root root 0 Nov 10 15:43 .. lrwxrwxrwx 1 root root 0 Nov 10 15:43 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Nov 10 15:47 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::scrolllock -> ../../devices/platform/i8042/serio0/input/input4/input4::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 phy0-led -> ../../devices/pci:00/:00:14.3/leds/phy0-led To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802495] Re: lttng-smoke test failed on i386 4.18 kernel
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802495 Title: lttng-smoke test failed on i386 4.18 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: New Bug description: There is one failure in the lttng-smoke test. FAILED (did not trace any open system calls) == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-15702-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == PASSED (lttng list --kernel) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-15702-session PASSED (lttng create) Kernel event open created in channel channel0 Kernel event openat created in channel channel0 Kernel event close created in channel channel0 PASSED (lttng enable-event) Tracing started for session test-kernel-session PASSED (lttng start) Waiting for data availability. Tracing stopped for session test-kernel-session PASSED (lttng stop) Session test-kernel-session destroyed PASSED (lttng destroy) FAILED (did not trace any open system calls) == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-15702-session PASSED (lttng create) Kernel event sched_switch created in channel channel0 PASSED (lttng enable-event) Tracing started for session test-kernel-session PASSED (lttng start) Waiting for data availability. Tracing stopped for session test-kernel-session PASSED (lttng stop) Session test-kernel-session destroyed PASSED (lttng destroy) Found 21349 dd and 73100 context switches PASSED (simple system call tracing with babeltrace) Summary: 13 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 NonfreeKernelModules: lttng_probe_writeback lttng_probe_workqueue lttng_probe_v4l2 lttng_probe_vmscan lttng_probe_udp lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sched lttng_probe_regulator lttng_probe_rcu lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net lttng_probe_napi lttng_probe_module lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq lttng_probe_gpio lttng_probe_compaction lttng_probe_block lttng_probe_asoc lttng_ring_buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client lttng_ring_buffer_client_overwrite lttng_ring_buffer_client_discard lttng_tracer lttng_statedump lttng_kprobes lttng_clock lttng_lib_ring_buffer lttng_kretprobes AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 9 11:35 seq crw-rw 1 root audio 116, 33 Nov 9 11:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Nov 9 11:51:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802495/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-gcp-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-gcp-edge source package in Bionic: Fix Released 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1802750 phase: Released phase-changed: Tuesday, 04. December 2018 07:06 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1789653
Title:
regression with EXT4 file systems and meta_bg flag
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
A regression was introduced where ext4_check_descriptors() was getting
called before s_gdb_count was initialized. This regression was
introduced to Xenial in 4.4.0-134. This is fixed by mainline commit
44de022c4382.
Commit 44de022c4382 was also cc'd to upstream stable. However, it has
not made it's way into Xenial via stable updates as of yet.
== Fix ==
44de022c4382 ("ext4: fix false negatives *and* false positives in
ext4_check_descriptors()")
== Regression Potential ==
Low. This commit has been cc'd upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Hello,
In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
partitions in ext4 with flag meta_bg :
kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap
for group 0 overlaps block group descriptors
kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
Go back with the kernel 4.4.0-133-generic and all partitions mount
correctly.
It looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
RelatedPackageVersions:
linux-restricted-modules-4.4.0-134-generic N/A
linux-backports-modules-4.4.0-134-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-134-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
RelatedPackageVersions:
[Kernel-packages] [Bug 1803206] Re: Please enable CONFIG_DMA_CMA=y on arm64
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803206 Title: Please enable CONFIG_DMA_CMA=y on arm64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Using the generic arm64 kernel on my raspberry pi 3 it seems impossible to use any apps that require 3D graphics. The X session crashes and a reboot is needed to make it bootable again. Inspecting dmesg, there are a lot of "failed to allocate CMA" messages. Adding cma=256M to the kernel command line has no effect. Dropping resolution allows firefox to start, but 3D apps still fail. I believe the vc4 driver needs CONFIG_DMA_CMA=y, which currently the generic kernel does not set. The raspi2 kernel has this and 3D graphics works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 Status in linux package in Ubuntu: Confirmed Bug description: The details of what I've attempted so far are in https://askubuntu.com/questions/1068161/clevo-n850el-crashes-freezes- ubuntu-18-04-1-frequently Any workaround help greatly appreciated. (I do not need NVIDIA graphics, but I do need VirtualBox). Regards, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpsl 1955 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 27 14:56:57 2018 InstallationDate: Installed on 2018-08-22 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2110 Acer, Inc Bus 001 Device 004: ID 0461:4de3 Primax Electronics, Ltd Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N8xxEL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text crashkernel=384M-:4096M RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.004 dmi.board.asset.tag: Tag 12345 dmi.board.name: N8xxEL dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.004:bd04/27/2018:svnNotebook:pnN8xxEL:pvrNotApplicable:rvnNotebook:rnN8xxEL:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N8xxEL dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802712] Re: Doesn't work a touchpad on Lenovo IdeaPad 330-15
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802712 Title: Doesn't work a touchpad on Lenovo IdeaPad 330-15 Status in linux package in Ubuntu: Fix Committed Bug description: I think the touchpad doesn't work on linux kernel 4.18 and less, because it works fine with kernel 4.19.1. I'm using Ubuntu 18.10 now. My laptop: https://psref.lenovo.com/Detail/Lenovo_Laptops/ideapad_330_15_Intel?M=81D1003SRU --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadim 1775 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 04f2:b5d7 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81D1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=b2094a80-83fb-4347-8097-74d998d093c1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0M26038 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IGM dmi.modalias: dmi:bvnLENOVO:bvr7XCN25WW:bd08/08/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0M26038WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM: dmi.product.family: ideapad 330-15IGM dmi.product.name: 81D1 dmi.product.sku: LENOVO_MT_81D1_BU_idea_FM_ideapad 330-15IGM dmi.product.version: Lenovo ideapad 330-15IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768761] Re: linux-snapdragon: reduce EPROBEDEFER noise during boot
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1768761 Title: linux-snapdragon: reduce EPROBEDEFER noise during boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: IMPACT: During boot, after the rootfs is mounted, the linux-snapdragon kernel prints several lines like these: ... [5.258027] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.258052] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [5.274320] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [5.274451] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops): -517 [5.300115] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.300140] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [5.733725] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [5.733841] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops): -517 [5.760228] qcom-apq8016-sbc 7702000.sound: error getting codec dai name [5.760252] qcom-apq8016-sbc 7702000.sound: Error resolving dai links: -517 [6.146074] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 ... these are the audio and drm modules failing to attach due to the adv7511 i2c bridge missing - they will retry several times, until the adv7511_drm is finally loaded and these messages disappear. While both audio and video work fine in the end, these lines make parsing the boot logs harder and might fool a user to think there's a potential problem. FIX: To fix it, make the config DRM_I2C_ADV7511=y. HOW TO REPRODUCE: Boot a patched kernel and check the boot logs. REGRESSION POTENTIAL: Probably none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773993] Re: Mouse cursor having a longer trail, lagging and stuttering
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773993 Title: Mouse cursor having a longer trail, lagging and stuttering Status in linux package in Ubuntu: Fix Released Bug description: Xubuntu 16.04.4, Kernel: 4.13.0-44 x86_64, CPU: i3-4030U, Graphics: Intel HD 4400. After kernel 4.13.0-40, my mouse cursor started to have a bigger trail then before, lagging and stutter during some load. During loading redhift mouse experience more lag. On a kernel 4.13.0-39 and 4.13.0-41 all good. I've tried to test on a various kernels and here are the results: Xubuntu 16.04.4, Kernel 4.13.0-39 = Good Xubuntu 16.04.4, Kernel 4.13.0-40 = Bad Xubuntu 16.04.4, Kernel 4.13.0-41 = Good Xubuntu 16.04.4, Kernel 4.13.0-42 = Bad Xubuntu 16.04.4, Kernel 4.13.0-43 = Bad Xubuntu 16.04.4, Kernel 4.13.0-44 = Bad Xubuntu 16.04.4, Kernel 4.15.18(Ubuntu mainline) = Bad Xubuntu 16.04.4, Kernel 4.16.4(Ubuntu mainline) = Bad Ubuntu 18.04, Kernel 4.15 = Bad Xubuntu 18.04, Kernel 4.16.10(Ubuntu mainline) = Bad Xubuntu 18.04, Kernel 4.16.11(Ubuntu mainline) = Bad Xubuntu 18.04, Kernel 4.16.12(Ubuntu mainline) = Bad Fedora 28, Kernel 4.16.3 = Bad OpenSuse Tumbleweed, Kernel 4.16.8 = Good Manjaro 17.1.9 KDE, Kernel 4.9.96 = Good Manjaro 17.1.9 KDE, Kernel 4.14.36 = Good Manjaro 17.1.9 KDE, Kernel 4.16.4 = Good Manjaro 17.1.9 KDE, Kernel 4.17.0-1 = Good Please request any information and tests that may help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-44-generic 4.13.0-44.49~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-44-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 29 17:03:15 2018 InstallationDate: Installed on 2017-07-23 (310 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: user 2320 F...m pulseaudio /dev/snd/controlC1: user 2320 F pulseaudio /dev/snd/controlC0: user 2320 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d969d8ec-87e0-493c-b317-4e68535c1b21 InstallationDate: Installed on 2017-07-23 (310 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-44-generic.efi.signed root=UUID=2bf2a7b1-cc88-4a21-aaca-251f52e78964 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-44-generic N/A linux-backports-modules-4.13.0-44-generic N/A linux-firmware 1.157.19 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: xenial Uname: Linux 4.13.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227D dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227D:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772610 Title: Adding back alx WoL feature Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] The WoL feature is a must to pass Energy Star 6.1 and above. The power consumption will be measured during S3 with WoL is enabled. [Test case] Verified pass on new Dell machines without the wake up issue. [Regression potential] No regression. We disable this feature by default, so the driver behavior will be the same. We'll leave this feature disabled by default before we can fix the unintentional wake up issue. [Misc] Upstream maintainer insists to fix the wake up issue before we can add this feature back to the driver, so make the patch stay in Ubuntu kernel only. We'll verify WoL on every new machines and try to fix this issue when we encounter it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1772610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806660 Title: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids Status in Linux: Confirmed Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello, The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids. In the upper part of gnome-shell it appears that they are with the headphones, and it is not like that. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio /dev/snd/pcmC0D0p: caravena 2784 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:59:27 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795662] Re: Linux 4.4.155 stable release build is broken on ppc64
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1795662
Title:
Linux 4.4.155 stable release build is broken on ppc64
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
The 4.4.y stable backport c9fadf27006b for upstream commit 1bd6a1c4b80a
("powerpc/fadump: handle crash memory ranges array index overflow"),
cherry-picked for Xenial as part of bug 1792419, introduces a build failure on
ppc by returning a int in a void function. In 4.4.y register_fadump() returns
void because 98b8cd7f7564 ("powerpc/fadump: Return error when fadump
registration fails") hasn't been backported for this stable release.
== Fix ==
98b8cd7f7564 ("powerpc/fadump: Return error when fadump registration fails")
== Regression Potential ==
Low. The patch only handles the error return by some function and adds an
additional error message. Limited to powerpc.
== Test Case ==
Compile the kernel for powerpc (tested with ppc64el).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
*** This bug is a duplicate of bug 1550779 *** https://bugs.launchpad.net/bugs/1550779 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 Updated docking station firmware to latest 2.33.00. PC temperatures are normal as per lm-sensors. 20171109 - Not reproducible testing drm-tip for 1.5 days. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1727662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802618] Re: linux-gcp-edge: 4.18.0-1003.4~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1802787 *** https://bugs.launchpad.net/bugs/1802787 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802618 Title: linux-gcp-edge: 4.18.0-1003.4~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.18.0-1003.4~18.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1799445 phase: Uploaded reason: promote-to-proposed: Ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682] Re: ACPI: Invalid passive threshold
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: New Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774282] Re: Bluetooth adapter not recognized
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774282 Title: Bluetooth adapter not recognized Status in linux package in Ubuntu: Confirmed Bug description: I have tried with both ubuntu 16.04 and today with 18.04 and the problem persists. I had the blueman installed and nothing works. On windows it works fine, so the adapter is not the issue. piero@piero-dev:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 Ubuntu Software 3.28.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 19:23:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-17 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-17 (227 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.0-041700rc7-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-05-30 (2 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10)
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen (18.04 & 18.10) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: // this bug was reported for 18.04. // I had just had it occur (first time) on 18.10 // new details will be comment @ end my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29
[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767857 Title: Kernel 4.4.0-122 Breaks qemu-system-x86 Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu- system-x86: black screen displays and qemu-system-x86 runs at 100% cpu indefinitely. Boot the same system with kernel 4.4.0-119 and qemu- system-x86 works fine running a Windows 10 VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic i686 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 29 15:58:25 2018 InstallationDate: Installed on 2014-04-29 (1460 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 394 2 0.0 [kvm-irqfd-clean] MachineType: Dell Inc. Inspiron 518 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash nmi_watchdog=0 SourcePackage: qemu UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago) dmi.bios.date: 03/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: 0K068D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 518 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794245] Re: Attached USB devices are ignored.
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794245 Title: Attached USB devices are ignored. Status in linux package in Ubuntu: Confirmed Bug description: After few suspends or detach-/attachments of USB devices libinput starts ignoring new devices due to too many input devices. Unnecessary to say there is only one device attached. journalctr reports this behavior: /usr/lib/gdm3/gdm-x-session[1407]: (**) PixArt USB Optical Mouse: always reports core events# /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "Device" "/dev/input/event295" /usr/lib/gdm3/gdm-x-session[1407]: (**) Option "_source" "server/udev" /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: is tagged by udev as: Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device set to 1000 DPI /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device is a pointer /usr/lib/gdm3/gdm-x-session[1407]: (II) event295 - PixArt USB Optical Mouse: device removed /usr/lib/gdm3/gdm-x-session[1407]: (EE) Too many input devices. Ignoring PixArt USB Optical Mouse /usr/lib/gdm3/gdm-x-session[1407]: (II) UnloadModule: "libinput" The bug seems related to a known libinput bug 1579567. https://bugzilla.redhat.com/show_bug.cgi?id=1579567 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-libinput 0.27.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 09:11:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: ASUSTeK COMPUTER INC. UX51VZA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=05aab5a7-bef4-4178-acea-7bebfacf8766 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX51VZA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX51VZA 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.:bvrUX51VZA.204:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnUX51VZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX51VZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802454
Title:
fanotify10 in ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
New
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== Justification ==
Commit 92183a42898d ("fsnotify: fix ignore mask logic in
send_to_group()") acknowledges the use case of ignoring an event on
an inode mark, because of an ignore mask on a mount mark of the same
group (i.e. I want to get all events on this file, except for the events
that came from that mount).
This change depends on correctly merging the inode marks and mount marks
group lists, so that the mount mark ignore mask would be tested in
send_to_group(). Alas, the merging of the lists did not take into
account the case where event in question is not in the mask of any of
the mount marks.
To fix this, completely remove the tests for inode and mount event masks
from the lists merging code.
== Fix ==
9bdda4e9 (fsnotify: fix ignore mask logic in fsnotify())
Test kernels for Bionic can be found here:
http://people.canonical.com/~phlin/kernel/lp-1802454-fanotify10/bionic/
It seems that T/X poses with the same issue and we might be able to backport
it with the same logic, but I think we should target Bionic as it's a fix for
for 92183a42898d which was only applied to Bionic.
== Regression Potential ==
Low.
The backport work is required as it's missing commit 47d9c7cc457 in Bionic,
which generalizes the iteration of marks for inode_mark and vfsmount_mark,
from:
iter_info.inode_mark
to:
iter_info.marks[FSNOTIFY_OBJ_TYPE_INODE]
But the patch can still be backported with the same logic without this
commit.
The test with the syscalls test in LTP test suite shows no sign of
regression.
== Test Case ==
Run the fanotify10 test in ubuntu_ltp_syscalls test suite. And it will pass
with the patched kernel.
Full LTP syscalls test with 4.15.0-42 in -proposed:
http://paste.ubuntu.com/p/Wm8nQ932g6/
Full LTP syscalls test with patched 4.15.0-42:
http://paste.ubuntu.com/p/nv4jW6shpJ/
-
This is a new test case that landed 7 days ago.
<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and
FAN_MARK_INODE ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and
FAN_MARK_MOUNT ignore mask
[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
6Wind is requesting these three patches. The patches fix a bug that prevents
a user
from following an interface that moves to another netns.
These commits are also needed in Xenial. However, they will be sent in
a separate SRU request due to additional prereq commits being needed for
Xenial.
== Fixes ==
b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
== Regression Potential ==
Medium due to three patches needed and the changes to core networking.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796453] Re: package linux-headers-generic 4.15.0.36.38 failed to install/upgrade: проблеми з залежностями - залишається неналаштованим
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796453 Title: package linux-headers-generic 4.15.0.36.38 failed to install/upgrade: проблеми з залежностями - залишається неналаштованим Status in linux package in Ubuntu: Confirmed Bug description: m ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-generic 4.15.0.36.38 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 18:48:04 2018 ErrorMessage: проблеми з залежностями - залишається неналаштованим HibernationDevice: RESUME=UUID=ae093d75-11a9-4320-b1f0-27ffc965f4c6 InstallationDate: Installed on 2018-09-14 (21 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=e27daf4b-b61a-4ba6-a72a-c6a906c7a2df ro i8042.nomux=1 i8042.reset quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 SourcePackage: linux-meta Title: package linux-headers-generic 4.15.0.36.38 failed to install/upgrade: проблеми з залежностями - залишається неналаштованим UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN17WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN17WW:bd07/13/2017:svnLENOVO:pn80XV:pvrLenovoideapad320-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-15AST: dmi.product.family: ideapad 320-15AST dmi.product.name: 80XV dmi.product.version: Lenovo ideapad 320-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729128] Re: Raspberry Pi 3 microSD support missing from the installer
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729128 Title: Raspberry Pi 3 microSD support missing from the installer Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] Without this module in block-modules.udeb, the default generic arm64 image cannot install on a raspberrypi3 board. [Test case] Build the block-modules.udeb with and without the attached patch and check for the presence of the drivers/mmc/host/bcm2835.ko. [Regression Potential] None, we are adding a ko to a udeb, not removing it. --- Please add bcm2835 to block-modules on arm64 (and armhf?). artful's arm64 d-i mini.iso works fine on Raspberry Pi 3 when booting with a UEFI-capable u-boot, except for one detail: mmc/host/bcm2835.ko is missing from block-modules, so you can't install to microSD without manually grabbing and loading the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795715] Re: Please apply upstream commit 87cdf3148b11d46382 to 4.15
*** This bug is a duplicate of bug 1795653 *** https://bugs.launchpad.net/bugs/1795653 ** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795715 Title: Please apply upstream commit 87cdf3148b11d46382 to 4.15 Status in linux package in Ubuntu: New Bug description: The commit [1] was applied to 4.16 but not marked for stable inclusion. It fixes commit [2] that was introduced in 4.15. Please include [1] in Bionic's 4.15 kernel. Not having it caused at least the following issues: * https://wiki.strongswan.org/issues/2571 * https://github.com/xelerance/xl2tpd/issues/160 1: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=87cdf3148b11 2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5efec5c655dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
