[Kernel-packages] [Bug 1825718] Re: Touchpad not detecting in Linux
https://lkml.org/lkml/2019/4/22/38 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825718 Title: Touchpad not detecting in Linux Status in linux package in Ubuntu: Confirmed Bug description: This issue was observed in laptop -"iBall-Aer3" which has a touch-pad with integrated fingerprint scanner. Both works very well in Windows 10, but not in Linux. Please Check. Any help is highly appreciated. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dipin 1204 F pulseaudio /dev/snd/controlC1: dipin 1204 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 18:12:35 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall Aer3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=53642f8a-ea5c-46e8-bde2-b1744102311b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G dmi.board.asset.tag: Default string dmi.board.name: Aer3 dmi.board.vendor: iBall dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Aer3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
in attach ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+attachment/5257830/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825718] Re: Touchpad not detecting in Linux
Okay..thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825718 Title: Touchpad not detecting in Linux Status in linux package in Ubuntu: Confirmed Bug description: This issue was observed in laptop -"iBall-Aer3" which has a touch-pad with integrated fingerprint scanner. Both works very well in Windows 10, but not in Linux. Please Check. Any help is highly appreciated. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dipin 1204 F pulseaudio /dev/snd/controlC1: dipin 1204 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 18:12:35 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall Aer3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=53642f8a-ea5c-46e8-bde2-b1744102311b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G dmi.board.asset.tag: Default string dmi.board.name: Aer3 dmi.board.vendor: iBall dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Aer3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822796 - phase: Testing - phase-changed: Thursday, 04. April 2019 00:34 UTC + phase: Ready for Testing + phase-changed: Monday, 22. April 2019 07:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1822794 Title: linux-kvm: 4.18.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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 promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1822796 phase: Ready for Testing phase-changed: Monday, 22. April 2019 07:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
The system use Nvidia graphics, please use "safe graphics mode" provided by the live usb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825699] Re: Touchpad not working after upgrade to 19.04
Please test this kernel: https://people.canonical.com/~khfeng/lp1825699/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825699 Title: Touchpad not working after upgrade to 19.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 the touch pad stopped working during the upgrade. cat /proc/bus/input/devices does not show any information about the Synaptics Touchpad. lsusb does show an entry: Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. synclient shows: Couldn't find synaptics properties. No synaptics driver loaded? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1990 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 08:32:38 2019 InstallationDate: Installed on 2019-04-10 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20LW0010GE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-20 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW0010GE 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:bvrR0QET49W(1.26):bd09/25/2018:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW0010GE dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Here is the output. I chose the keyboard output since the hp modules didn't generate any output. The events for VOLUME_UP, VOLUME_DOWN and MUTE are working as expected. The last two outputs are of the BRIGHTNESS_UP and _DOWN combinations (FN+F4 and FN+F3) and seem to be exactly the same ** Attachment added: "evtest.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+attachment/5257850/+files/evtest.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 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.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+
** Changed in: hwe-next Status: New => Fix Released -- 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/1817848 Title: i915: Backport watermark fixes for gen9+ Status in HWE Next: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] 5.0 fixes screen flicker issues with new panel models and on hybrid machines, and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ cherry-picked commits plus a handful of build fixes: git://github.com/vsyrjala/linux.git skl_wm_backport_4.15 [Test case] Various display configurations with an external monitor connected need to be tested, preferably on a wider set of hardware [Regression potential] The backport was done by Intel, and tested with intel-gpu-tools to do the right thing, but there's always a chance of regressing something. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790835] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1790832 *** https://bugs.launchpad.net/bugs/1790832 --- Comment From vipar...@in.ibm.com 2019-04-22 03:51 EDT--- Hello Canonical, Is this fix available in any Ubuntu releases ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790835 Title: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2018-09-04 15:07:23 == Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
Tested with the latest selftest in Linus' tree, this test will pass. So this looks like a test case issue to me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812809 Title: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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 ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el 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 Jan 22 07:11:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812809 Title: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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 ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el 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 Jan 22 07:11:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root h
[Kernel-packages] [Bug 1790835] Re: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs
*** This bug is a duplicate of bug 1790832 *** https://bugs.launchpad.net/bugs/1790832 As you can see from top of this Launchpad ticket (page): "This bug report is a duplicate of: Bug #1790832: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04." this ticket was marked as a duplicate of LP 1790832: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790832 and with that this ticket LP 1790835 is no longer updated, but LP 1790832 is. And LP 1790832 is in state "Fixed Released" for Xenial, Bionic and Cosmic - hence this fix is included in virtually all available Ubuntu releases that are in (base) service (incl. Disco). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790835 Title: Ubuntu18.10 - crypto/vmx: Fix sleep-in-atomic bugs Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: == Comment: #0 - Paulo Flabiano Smorigo - 2018-09-04 15:07:23 == Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812809 Title: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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 ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el 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 Jan 22 07:11:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Found
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
** Description changed: + == Justification == + When running the ftrace in ubunut_kernel_selftests, the "Kprobe event argument syntax" will fail on Bionic PowerPC. + + This is because PowerPC was not supported by this test. + + == Fix == + 9855c462 (selftests/ftrace: Add ppc support for kprobe args tests) + + == Test == + Patch tested with Bionic P8. Test passed as expected: + [23] Kprobe event argument syntax [PASS] + + == Regression potential == + None. + This patch is just for the kernel testing tool.. + + + == Original bug report == This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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 ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el 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 Jan 22 07:11:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
https://lkml.org/lkml/2019/4/22/81 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59 taplop kernel: Freezing user space pro
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
Yes, please use my custom built kernel in the interim. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop kernel: PM: suspend entry (deep) Apr 02 13:39:59 taplop kernel: PM: Syncing filesystems ... done. Apr 02 13:39:59 taplop kernel: Fre
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
** Description changed: == Justification == When running the ftrace in ubunut_kernel_selftests, the "Kprobe event argument syntax" will fail on Bionic PowerPC. This is because PowerPC was not supported by this test. == Fix == 9855c462 (selftests/ftrace: Add ppc support for kprobe args tests) + This patch can be cherry-picked for Bionic and Xenial. + Although we don't run this ftrace test in Xenial, it will still be a plus to fix this. + + It's already been applied in C/D. == Test == Patch tested with Bionic P8. Test passed as expected: [23] Kprobe event argument syntax [PASS] == Regression potential == None. This patch is just for the kernel testing tool. - == Original bug report == This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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 ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el 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 Jan 22 07:11:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb:
[Kernel-packages] [Bug 1812809] Re: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC
** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812809 Title: Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed on B PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: == Justification == When running the ftrace in ubunut_kernel_selftests, the "Kprobe event argument syntax" will fail on Bionic PowerPC. This is because PowerPC was not supported by this test. == Fix == 9855c462 (selftests/ftrace: Add ppc support for kprobe args tests) This patch can be cherry-picked for Bionic and Xenial. Although we don't run this ftrace test in Xenial, it will still be a plus to fix this. It's already been applied in C/D. == Test == Patch tested with Bionic P8. Test passed as expected: [23] Kprobe event argument syntax [PASS] == Regression potential == None. This patch is just for the kernel testing tool. == Original bug report == This issue was not spotted on the other arches. Failure: [23] Kprobe event argument syntax [FAIL] === 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 [PASS] [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 [PASS] [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 [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 49 # of failed: 1 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 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
[Kernel-packages] [Bug 1825813] [NEW] Need to add AMD Stony Ridge APU support to Xenial
Public bug reported: AMD suggested to back port the following fixes in 4.18 kernel needed to support AMD Stony Ridge APU to Xenial: drm/amdgpu/vcn: Update vcn.cur_state during suspend drm/amd/display: Fix BUG_ON during CRTC atomic check update ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New -- 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/1825813 Title: Need to add AMD Stony Ridge APU support to Xenial Status in linux-oem package in Ubuntu: New Bug description: AMD suggested to back port the following fixes in 4.18 kernel needed to support AMD Stony Ridge APU to Xenial: drm/amdgpu/vcn: Update vcn.cur_state during suspend drm/amd/display: Fix BUG_ON during CRTC atomic check update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1825813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825813] Re: Need to add AMD Stony Ridge APU support to Bionic
** Summary changed: - Need to add AMD Stony Ridge APU support to Xenial + Need to add AMD Stony Ridge APU support to Bionic ** Description changed: AMD suggested to back port the following fixes in 4.18 kernel needed to - support AMD Stony Ridge APU to Xenial: - + support AMD Stony Ridge APU to Bionic: drm/amdgpu/vcn: Update vcn.cur_state during suspend drm/amd/display: Fix BUG_ON during CRTC atomic check update -- 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/1825813 Title: Need to add AMD Stony Ridge APU support to Bionic Status in linux-oem package in Ubuntu: New Bug description: AMD suggested to back port the following fixes in 4.18 kernel needed to support AMD Stony Ridge APU to Bionic: drm/amdgpu/vcn: Update vcn.cur_state during suspend drm/amd/display: Fix BUG_ON during CRTC atomic check update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1825813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
No. The issue remains. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V 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.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825780] Re: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386
This issue can be fixed by patch: https://github.com/torvalds/linux/commit/6fc7c4110cbaff85b1f49fd70b77950384c3a201 It's already in Disco. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825780 Title: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Failure spotted on Bionic / Cosmic i386 (node fozzie) [22] Kprobe event string type argument [FAIL] selftests: ftrace: 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] Snapshot and tracing setting [PASS] [6] event tracing - enable/disable with event level files[PASS] [7] event tracing - restricts events based on pid[PASS] [8] event tracing - enable/disable with subsystem level files[PASS] [9] event tracing - enable/disable with top level files [PASS] [10] ftrace - function graph filters with stack tracer [PASS] [11] ftrace - function graph filters [PASS] [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 [FAIL] [23] Kprobe event argument syntax[PASS] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer [PASS] [27] Kretprobe dynamic event with arguments [PASS] [28] Kretprobe dynamic event with maxactive [PASS] [29] Register/unregister many kprobe events [PASS] [30] event trigger - test extended error support [PASS] [31] event trigger - test field variable support [PASS] [32] event trigger - test multiple actions on hist trigger [PASS] [33] event trigger - test inter-event histogram trigger onmatch action [PASS] [34] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [35] event trigger - test inter-event histogram trigger onmax action [PASS] [36] event trigger - test synthetic_events syntax parser [PASS] [37] event trigger - test event enable/disable trigger [PASS] [38] event trigger - test trigger filter [PASS] [39] event trigger - test histogram modifiers[PASS] [40] event trigger - test multiple histogram triggers[PASS] [41] event trigger - test snapshot-trigger [PASS] [42] event trigger - test stacktrace-trigger [PASS] [43] trace_marker trigger - test snapshot trigger[PASS] [44] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] [45] trace_marker trigger - test histogram with synthetic event [PASS] [46] event trigger - test traceon/off trigger[PASS] [47] (instance) Basic test for tracers [PASS] [48] (instance) Basic trace clock test [PASS] [49] (instance) Snapshot and tracing setting [PASS] [50] (instance) event tracing - enable/disable with event level files [PASS] [51] (instance) event tracing - restricts events based on pid[PASS] [52] (instance) event tracing - enable/disable with subsystem level files [PASS] [53] (instance) ftrace - test for function event triggers[PASS] [54] (instance) ftrace - test for function traceon/off triggers [PASS] [55] (instance) event trigger - test event enable/disable trigger[PASS] [56] (instance) event trigger - test trigger fil
[Kernel-packages] [Bug 1825638] Re: Lenovo Legion Y530-15ICH does not start with live usb
Thanks, partially helped. Ubuntu starts up normally, Kubuntu doesn’t run, which is a pity, because KDE I already like a lot more. I will stay at the Manjaro. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825638 Title: Lenovo Legion Y530-15ICH does not start with live usb Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y530-15ICH does not start with live usb Does not load beyond the boot screen with the Ubuntu logo the same situation is with Kubuntu, but it loads up to the desktop image, the interface is not loaded Actually on the versions of Ubuntu / Kubuntu: 18.04, 18.10, 19.04 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz lspci-vnvn.log make in Manjaro linux (it works well), but I would like to use Ubuntu / Kubuntu (preferably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825780] Re: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386
** Description changed: + == Justification == + When running the ftrace in ubunut_kernel_selftests, the "Kprobe event string type argument" will fail on Bionic / Cosmic i386: + [22] Kprobe event string type argument [FAIL] + + + == Fix == + 6fc7c411 (selftests/ftrace: Fix kprobe string testcase to not probe notrace function) + + This patch can be cherry-picked for Cosmic. + + For Bionic and Xenial, it can be cherry-picked after the commit 9855c462 + for bug 1812809 + + Although we don't run this ftrace test in Xenial, it will still be a + plus to fix this. + + It's already been applied in D. + + == Test == + Patch tested with Bionic / Cosmic i386. Test passed as expected: + [22] Kprobe event string type argument [PASS] + + + == Regression potential == + None. + This patch is just for the kernel testing tool. + + + == Original bug report == Failure spotted on Bionic / Cosmic i386 (node fozzie) [22] Kprobe event string type argument [FAIL] + selftests: ftrace: 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] Snapshot and tracing setting [PASS] + [6] event tracing - enable/disable with event level files[PASS] + [7] event tracing - restricts events based on pid[PASS] + [8] event tracing - enable/disable with subsystem level files[PASS] + [9] event tracing - enable/disable with top level files [PASS] + [10] ftrace - function graph filters with stack tracer [PASS] + [11] ftrace - function graph filters [PASS] + [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 [FAIL] + [23] Kprobe event argument syntax[PASS] + [24] Kprobes event arguments with types [PASS] + [25] Kprobe event auto/manual naming [PASS] + [26] Kprobe dynamic event with function tracer [PASS] + [27] Kretprobe dynamic event with arguments [PASS] + [28] Kretprobe dynamic event with maxactive [PASS] + [29] Register/unregister many kprobe events [PASS] + [30] event trigger - test extended error support [PASS] + [31] event trigger - test field variable support [PASS] + [32] event trigger - test multiple actions on hist trigger [PASS] + [33] event trigger - test inter-event histogram trigger onmatch action [PASS] + [34] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] + [35] event trigger - test inter-event histogram trigger onmax action [PASS] + [36] event trigger - test synthetic_events syntax parser [PASS] + [37] event trigger - test event enable/disable trigger [PASS] + [38] event trigger - test trigger filter [PASS] + [39] event trigger - test histogram modifiers[PASS] + [40] event trigger - test multiple histogram triggers[PASS] + [41] event trigger - test snapshot-trigger [PASS] + [42] event trigger - test stacktrace-trigger [PASS] + [43] trace_marker trigger - test snapshot trigger[PASS] + [44] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] + [45] trace_marker trigger - test histogram with synthetic event [PASS] + [46] event trigger - test traceon/off trigger[PASS] + [47] (instance) Basic test for tracers [PASS] + [48] (instance) Basic trace clock test [PASS] + [49] (instance) Snapshot and tracing setting [PASS] + [50] (instance) event tracing - enable/disable with event level files [PASS] + [51] (instance) event tracing - restricts events based on pid[PASS] + [52] (instance) event tracing - enable/disable with subsystem level files [PASS] + [53] (instance) ftrace - test for function event triggers[PASS] + [54] (instance) ftrace - test for function traceon/off triggers [PASS] + [55] (instance) event trigger - test event enable/disable trigger[PASS] + [56] (instance) event trigger - test trigger filter [PASS] + [57] (instance) event trigger - test histogram modifiers [PASS] + [58] (instance) event trigger - test multiple histogram triggers [PASS] + [59] (instance) trace_marker trigger - test snapshot trigger [PASS] - selftests: ftrace: ftracetest - - === Ftrace unit
[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816394 Title: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol) Status in linux package in Ubuntu: New Bug description: Ubuntu 19.04 QA-Test (LIVE x86_64) Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT) Two dell displays, left is landscape, right is portrait This live test had two packages added: `vim` & `ubuntu-restricted- extras` Background: I added ubuntu-restricted-extras so I could run requested test on this system which had me streaming videos from utube - it was required to get around H264 errors (vim because I can't cope with other editors & added `multiverse` to my sources. Issue: With firefox streaming ABC News 24 (local AU news) I suspended machine. Waited Awoke machine - everything resumed as expected .. Some circling was apparent on firefox before picture resumed, however no sound. I was unable to fix it using any tools installed - to fix I `sudo apt install pavucontrol`, went to Configuration (or last tab) and Profile=Off on the drop-down menu, then returned to Profile=AnalogStereo Duplex. This is something I do on occasion for this machine on installed system or other machines I use. This is really a minor issue, & may not be an issue on an installed system (though I come across it semi-regularly & just live with it). In regular use I pause/stop sound & know this makes this almost a non- issue (almost never happens when sound isn't playing). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 11:01:59 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825821] [NEW] Ubuntu 16.04 : Bluetooth can't be detected by other devices
Public bug reported: Hi, I am running an Ubuntu 16.04 machine. I tried to start the system bluetooth through the following steps: 1. Ensured that bluetooth was unblocked through the command rfkill 2. Set bluetooth to powered on, agent on, default-agent and scan on through bluetootctl On completing these steps, Bluetooth icon shows up as active on the system, but other devices are unable to scan it and consequently not able to connect to it. This Ubuntu does not appear in the list of bluetooth devices for other devices' scan. 3. I ran systemctl status bluetooth I am getting the following errors: nvidia@tegra-ubuntu:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-04-22 15:57:21 IST; 10min ago Docs: man:bluetoothd(8) Main PID: 1087 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─1087 /usr/lib/bluetooth/bluetoothd Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Error adding Link Loss service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Current Time Service could not be registered Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: gatt-time-server: Input/output error (5) Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Sap driver initialization failed. Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: sap-server: Operation not permitted (1) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825821 Title: Ubuntu 16.04 : Bluetooth can't be detected by other devices Status in bluez package in Ubuntu: New Bug description: Hi, I am running an Ubuntu 16.04 machine. I tried to start the system bluetooth through the following steps: 1. Ensured that bluetooth was unblocked through the command rfkill 2. Set bluetooth to powered on, agent on, default-agent and scan on through bluetootctl On completing these steps, Bluetooth icon shows up as active on the system, but other devices are unable to scan it and consequently not able to connect to it. This Ubuntu does not appear in the list of bluetooth devices for other devices' scan. 3. I ran systemctl status bluetooth I am getting the following errors: nvidia@tegra-ubuntu:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-04-22 15:57:21 IST; 10min ago Docs: man:bluetoothd(8) Main PID: 1087 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─1087 /usr/lib/bluetooth/bluetoothd Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Error adding Link Loss service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Current Time Service could not be registered Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: gatt-time-server: Input/output error (5) Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Sap driver initialization failed. Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: sap-server: Operation not permitted (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816394] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1816394 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816394 Title: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol) Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 QA-Test (LIVE x86_64) Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT) Two dell displays, left is landscape, right is portrait This live test had two packages added: `vim` & `ubuntu-restricted- extras` Background: I added ubuntu-restricted-extras so I could run requested test on this system which had me streaming videos from utube - it was required to get around H264 errors (vim because I can't cope with other editors & added `multiverse` to my sources. Issue: With firefox streaming ABC News 24 (local AU news) I suspended machine. Waited Awoke machine - everything resumed as expected .. Some circling was apparent on firefox before picture resumed, however no sound. I was unable to fix it using any tools installed - to fix I `sudo apt install pavucontrol`, went to Configuration (or last tab) and Profile=Off on the drop-down menu, then returned to Profile=AnalogStereo Duplex. This is something I do on occasion for this machine on installed system or other machines I use. This is really a minor issue, & may not be an issue on an installed system (though I come across it semi-regularly & just live with it). In regular use I pause/stop sound & know this makes this almost a non- issue (almost never happens when sound isn't playing). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 11:01:59 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 - phase: Testing - phase-changed: Wednesday, 17. April 2019 08:26 UTC + phase: Ready for Testing + phase-changed: Monday, 22. April 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress -- 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/1824771 Title: linux-aws: 4.18.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Ready for Testing phase-changed: Monday, 22. April 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816394] Re: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol)
Live QA-Test so I'm almost certain a new of test would not create identical trace details for the issue. This condition occurs about once a fortnight on my primary box (the d960 in list of machines it occurs on) but that system is somewhat modified (with loads more packages installed). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816394 Title: Ubuntu 19.04 qa:test - suspended system resumed without audio (i fixed via add of pavucontrol) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 QA-Test (LIVE x86_64) Dell optiplex d755, (c2d-e8300, 8gb, Radeon HD 2400 PRO/XT) Two dell displays, left is landscape, right is portrait This live test had two packages added: `vim` & `ubuntu-restricted- extras` Background: I added ubuntu-restricted-extras so I could run requested test on this system which had me streaming videos from utube - it was required to get around H264 errors (vim because I can't cope with other editors & added `multiverse` to my sources. Issue: With firefox streaming ABC News 24 (local AU news) I suspended machine. Waited Awoke machine - everything resumed as expected .. Some circling was apparent on firefox before picture resumed, however no sound. I was unable to fix it using any tools installed - to fix I `sudo apt install pavucontrol`, went to Configuration (or last tab) and Profile=Off on the drop-down menu, then returned to Profile=AnalogStereo Duplex. This is something I do on occasion for this machine on installed system or other machines I use. This is really a minor issue, & may not be an issue on an installed system (though I come across it semi-regularly & just live with it). In regular use I pause/stop sound & know this makes this almost a non- issue (almost never happens when sound isn't playing). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 11:01:59 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825229] Re: linux-oracle: Use upstream approach to fix a race when hot adding a VF
** Summary changed: - request to supercede the interim changes for 1815268 with upstream commit 8065a779 + linux-oracle: Use upstream approach to fix a race when hot adding a VF ** Description changed: + [Impact] + The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. + + [Test Case] + + Sane as bug #1815268 + + [Regression Potential] + + The proposed solution introduces low risk of regression because it only + affects the linux-oracle kernel on instances using net_failover. + + [Misc] + + Original title: "request to supercede the interim changes for 1815268 + with upstream commit 8065a779" ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux-oracle (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-oracle (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Bionic) Importance: Undecided => High ** Description changed: [Impact] The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. [Test Case] - Sane as bug #1815268 + Same as bug #1815268 [Regression Potential] The proposed solution introduces low risk of regression because it only affects the linux-oracle kernel on instances using net_failover. [Misc] Original title: "request to supercede the interim changes for 1815268 with upstream commit 8065a779" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825229 Title: linux-oracle: Use upstream approach to fix a race when hot adding a VF Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Bionic: In Progress Bug description: [Impact] The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. [Test Case] Same as bug #1815268 [Regression Potential] The proposed solution introduces low risk of regression because it only affects the linux-oracle kernel on instances using net_failover. [Misc] Original title: "request to supercede the interim changes for 1815268 with upstream commit 8065a779" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1825229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825229] Re: linux-oracle: Use upstream approach to fix a race when hot adding a VF
https://lists.ubuntu.com/archives/kernel-team/2019-April/100252.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1825229 Title: linux-oracle: Use upstream approach to fix a race when hot adding a VF Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Bionic: In Progress Bug description: [Impact] The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. [Test Case] Same as bug #1815268 [Regression Potential] The proposed solution introduces low risk of regression because it only affects the linux-oracle kernel on instances using net_failover. [Misc] Original title: "request to supercede the interim changes for 1815268 with upstream commit 8065a779" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1825229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Confirmed Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813651] Re: hpsa: DMAR invalid read
Hi Terry, I'm planning to post an update this week. It seems the problem is related with physical block size adjustments, after the introduction of the patch: "eb53a3ea3e00 scsi: hpsa: limit transfer length to 1MB, not 512kB" Without this patch I don't see the issue anymore. But I'm investigating why this patch triggers the issue... Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813651 Title: hpsa: DMAR invalid read Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: Recently in kernel 4.20-rc1 and newer we observed the following spontaneous issue with hpsa when intel_iommu is enabled: [ 5173.952022] DMAR: DRHD: handling fault status reg 2 [ 5174.190649] DMAR: [DMA Read] Request device [03:00.0] fault addr eefdd000 [fault reason 06] PTE Read access is not set There's a commit that touches DMA in hpsa: "scsi: hpsa: switch to generic DMA API" We've tested with this commit reverted on top of 4.20-rc1 and it reproduces (the trigger is a kernel build). We cannot reproduce in 4.19. Investigation is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825841] [NEW] Laptop battery drains while suspend since 18.04 , even in deep sleep (STR)
Public bug reported: Hi, 1) My laptop battery drains very fast while suspend, which prevent using suspend-to-ram as I almost always find the laptop shut down due to battery being empty. I Observed this problem since my upgrade from 16.04 to 18.04 on my Laptop. It's Toshiba Portege. Suspend does work fine but battery drains while suspend; it was working pretty well in Ubuntu 16.04. I suspect a kind of regression in the i915 driver for now, but did not find any evident of this. After a suspend to ram, we can observe a kind of crash in the i915 driver suspend_late code : [ 475.970946] [ cut here ] [ 475.970947] Display power well on [ 475.971009] WARNING: CPU: 0 PID: 7579 at /build/linux-6ZmFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:8696 assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971010] Modules linked in: rfcomm ccm cmac bnep cdc_mbim uvcvideo cdc_wdm qcserial cdc_ncm usb_wwan usbserial usbnet mii btusb btrtl btbcm videobuf2_vmalloc btintel videobuf2_memops videobuf2_v4l2 videobuf2_core bluetooth videodev media ecdh_generic msr arc4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel kvm mac80211 irqbypass snd_seq intel_cstate intel_rapl_perf iwlwifi snd_seq_device snd_timer joydev cfg80211 input_leds serio_raw wmi_bmof snd rtsx_pci_ms memstick lpc_ich shpchp mei_me toshiba_acpi mei soundcore sparse_keymap toshiba_bluetooth industrialio tpm_infineon mac_hid sch_fq_codel parport_pc [ 475.971045] ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm rtsx_pci ptp pps_core video wmi [ 475.971062] CPU: 0 PID: 7579 Comm: kworker/u16:7 Not tainted 4.15.0-47-generic #50-Ubuntu [ 475.971063] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS Version 3.20 04/09/2015 [ 475.971066] Workqueue: events_unbound async_run_entry_fn [ 475.971087] RIP: 0010:assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971088] RSP: 0018:a96642bbfd00 EFLAGS: 00010286 [ 475.971089] RAX: RBX: 9bf98b0a8000 RCX: bca62768 [ 475.971090] RDX: bca62768 RSI: 0082 RDI: 0202 [ 475.971091] RBP: a96642bbfd20 R08: R09: 0015 [ 475.971091] R10: 0600 R11: 0340 R12: 9bf98b0a8358 [ 475.971092] R13: 9bf98b0a8368 R14: c0580baf R15: [ 475.971093] FS: () GS:9bf9a140() knlGS: [ 475.971094] CS: 0010 DS: ES: CR0: 80050033 [ 475.971095] CR2: 7fb1afffeeb6 CR3: 00011e20a005 CR4: 003606f0 [ 475.971096] Call Trace: [ 475.971117] hsw_enable_pc8+0x87/0x310 [i915] [ 475.971129] i915_drm_suspend_late+0xdb/0x140 [i915] [ 475.971141] i915_pm_suspend_late+0x20/0x30 [i915] [ 475.971143] pm_generic_suspend_late+0x2e/0x40 [ 475.971145] pci_pm_suspend_late+0x31/0x40 [ 475.971147] dpm_run_callback+0x5a/0x150 [ 475.971149] ? pci_pm_poweroff_late+0x40/0x40 [ 475.971151] __device_suspend_late+0xc6/0x1d0 [ 475.971152] async_suspend_late+0x1f/0xa0 [ 475.971154] async_run_entry_fn+0x3c/0x150 [ 475.971156] process_one_work+0x1de/0x410 [ 475.971158] worker_thread+0x32/0x410 [ 475.971160] kthread+0x121/0x140 [ 475.971161] ? process_one_work+0x410/0x410 [ 475.971163] ? kthread_create_worker_on_cpu+0x70/0x70 [ 475.971166] ret_from_fork+0x35/0x40 [ 475.971167] Code: d5 ff 48 8b 83 18 07 00 00 e9 b0 fd ff ff 89 ce 4c 89 f7 e8 90 fc 1a fb 0f 0b e9 99 fc ff ff 48 c7 c7 c9 0b 58 c0 e8 7d fc 1a fb <0f> 0b e9 b5 fc ff ff 48 c7 c7 7a 0c 58 c0 e8 6a fc 1a fb 0f 0b [ 475.971192] ---[ end trace 91209fe53f0c0cc2 ]--- By using a more recent kernel (4.18), I get a crash in the pc8 disable function. I am not sure whether this thread backtrace is responsible for the battery drain or not. I also read Intel open source site to help debug this, without success for now : * https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues The analyze_suspend.py script produced some bunch of data, if anyone needs them to understand what's happening while system is suspended, I can publish them. Other sources of information I consulted : * https://askubuntu.com/questions/1072066/sleep-mode-drains-battery- very-fast * https://www.reddit.com/r/Dell/comments/8b6eci/xp_13_9370_battery_drain_while_suspended/ I confirm my system is going to "deep" sleep and not "s2idle" sleep mode, which would explain the battery drain... Other information : Description:Ubuntu 18.04.1 LTS Release:
[Kernel-packages] [Bug 1789949] Re: WiFi-Stick TP-Link T2UH not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789949 Title: WiFi-Stick TP-Link T2UH not working Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: TP-Link Archer T2UH, AC600, version 1 After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 10 I was immediately able to connect). So searching on the web I found some kind of "solution", which it not really working well. on various Forums I found the links to the following drivers: https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916 https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/ From which the first works well on Debian, but fail to compile on ubuntu. And the second one works on ubuntu, but makes the network manager laggin, and won't let me reconnect after some random disconnects, until I restart the NetworkManager.That happens quite often. Plugging it out and back in, also requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, I had to manually copy-paste the git, cause the readme description seemed to be referring to another package. Also, I don't know how secure these drivers are. There is also a driver from TP-Link, which is too old and doesnt work with newer kernels. Mediatek also has driver, but i didnt know how to build them. Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick (thus showing "no networks") and im connected to the internet through another (built-in) device. For the TP-Link T2UH the lsusb will show: Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. while disconnected the "ip a" will show: 9: ra0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff lsb_release -rd shows: Description: Ubuntu 18.04.1 LTS Release: 18.04 Not sure if this is a bug of the Network Manager, or just a missing feature. Maybe it would be good to have a driver for it from the repository. Or to somehow integrate the chip-support into the system. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 17:51:16 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-26 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/4 uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7 /org/freedesktop/NetworkManager/ActiveConnection/7 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- ra0 wifi unmanaged/org/freedesktop/NetworkManager/Devices/5 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: a 2175 F pulseaudio /dev/snd/pcmC0D0p: a 2175 F...m pulseaudio /dev/snd/controlC0: a 2175 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-26 (1
[Kernel-packages] [Bug 1825229] Re: linux-oracle: Use upstream approach to fix a race when hot adding a VF
** Changed in: linux-oracle (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1825229 Title: linux-oracle: Use upstream approach to fix a race when hot adding a VF Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Bionic: Fix Committed Bug description: [Impact] The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. [Test Case] Same as bug #1815268 [Regression Potential] The proposed solution introduces low risk of regression because it only affects the linux-oracle kernel on instances using net_failover. [Misc] Original title: "request to supercede the interim changes for 1815268 with upstream commit 8065a779" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1825229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806973] Re: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1806973 Title: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But ZFS did work OK after upgrade. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: zfs-dkms 0.7.9-3ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 DKMSBuildLog: DKMS make.log for zfs-0.7.9 for kernel 4.18.0-12-generic (x86_64) Wed Dec 5 13:43:02 AST 2018 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 4.18.0-12-generic Date: Wed Dec 5 13:43:04 2018 InstallationDate: Installed on 2018-01-11 (328 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all PackageVersion: 0.7.9-3ubuntu6 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: zfs-linux Title: zfs-dkms 0.7.9-3ubuntu6: zfs kernel module failed to build UpgradeStatus: Upgraded to cosmic on 2018-12-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1806973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825841] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825841 Title: Laptop battery drains while suspend since 18.04 , even in deep sleep (STR) Status in linux package in Ubuntu: Confirmed Bug description: Hi, 1) My laptop battery drains very fast while suspend, which prevent using suspend-to-ram as I almost always find the laptop shut down due to battery being empty. I Observed this problem since my upgrade from 16.04 to 18.04 on my Laptop. It's Toshiba Portege. Suspend does work fine but battery drains while suspend; it was working pretty well in Ubuntu 16.04. I suspect a kind of regression in the i915 driver for now, but did not find any evident of this. After a suspend to ram, we can observe a kind of crash in the i915 driver suspend_late code : [ 475.970946] [ cut here ] [ 475.970947] Display power well on [ 475.971009] WARNING: CPU: 0 PID: 7579 at /build/linux-6ZmFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:8696 assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971010] Modules linked in: rfcomm ccm cmac bnep cdc_mbim uvcvideo cdc_wdm qcserial cdc_ncm usb_wwan usbserial usbnet mii btusb btrtl btbcm videobuf2_vmalloc btintel videobuf2_memops videobuf2_v4l2 videobuf2_core bluetooth videodev media ecdh_generic msr arc4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel kvm mac80211 irqbypass snd_seq intel_cstate intel_rapl_perf iwlwifi snd_seq_device snd_timer joydev cfg80211 input_leds serio_raw wmi_bmof snd rtsx_pci_ms memstick lpc_ich shpchp mei_me toshiba_acpi mei soundcore sparse_keymap toshiba_bluetooth industrialio tpm_infineon mac_hid sch_fq_codel parport_pc [ 475.971045] ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm rtsx_pci ptp pps_core video wmi [ 475.971062] CPU: 0 PID: 7579 Comm: kworker/u16:7 Not tainted 4.15.0-47-generic #50-Ubuntu [ 475.971063] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS Version 3.20 04/09/2015 [ 475.971066] Workqueue: events_unbound async_run_entry_fn [ 475.971087] RIP: 0010:assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971088] RSP: 0018:a96642bbfd00 EFLAGS: 00010286 [ 475.971089] RAX: RBX: 9bf98b0a8000 RCX: bca62768 [ 475.971090] RDX: bca62768 RSI: 0082 RDI: 0202 [ 475.971091] RBP: a96642bbfd20 R08: R09: 0015 [ 475.971091] R10: 0600 R11: 0340 R12: 9bf98b0a8358 [ 475.971092] R13: 9bf98b0a8368 R14: c0580baf R15: [ 475.971093] FS: () GS:9bf9a140() knlGS: [ 475.971094] CS: 0010 DS: ES: CR0: 80050033 [ 475.971095] CR2: 7fb1afffeeb6 CR3: 00011e20a005 CR4: 003606f0 [ 475.971096] Call Trace: [ 475.971117] hsw_enable_pc8+0x87/0x310 [i915] [ 475.971129] i915_drm_suspend_late+0xdb/0x140 [i915] [ 475.971141] i915_pm_suspend_late+0x20/0x30 [i915] [ 475.971143] pm_generic_suspend_late+0x2e/0x40 [ 475.971145] pci_pm_suspend_late+0x31/0x40 [ 475.971147] dpm_run_callback+0x5a/0x150 [ 475.971149] ? pci_pm_poweroff_late+0x40/0x40 [ 475.971151] __device_suspend_late+0xc6/0x1d0 [ 475.971152] async_suspend_late+0x1f/0xa0 [ 475.971154] async_run_entry_fn+0x3c/0x150 [ 475.971156] process_one_work+0x1de/0x410 [ 475.971158] worker_thread+0x32/0x410 [ 475.971160] kthread+0x121/0x140 [ 475.971161] ? process_one_work+0x410/0x410 [ 475.971163] ? kthread_create_worker_on_cpu+0x70/0x70 [ 475.971166] ret_from_fork+0x35/0x40 [ 475.971167] Code: d5 ff 48 8b 83 18 07 00 00 e9 b0 fd ff ff 89 ce 4c 89 f7 e8 90 fc 1a fb 0f 0b e9 99 fc ff ff 48 c7 c7 c9 0b 58 c0 e8 7d fc 1a fb <0f> 0b e9 b5 fc ff ff 48 c7 c7 7a 0c 58 c0 e8 6a fc 1a fb 0f 0b [ 475.971192] ---[ end trace 91209fe53f0c0cc2 ]--- By using a more recent kernel (4.18), I get a crash in the pc8 disable function. I am not sure whether this thread backtrace is responsible for the battery drain or not. I also read Intel open source site to help debug this, without success for now : * https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues The analyze_suspend.py script produced some bunch of da
[Kernel-packages] [Bug 1821378] Re: [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
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/1821378
Title:
[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
in Azure kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
New
Status in linux-azure source package in Cosmic:
New
Bug description:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.
The result is accessing a bogus memory address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825632] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
This looks to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420 Can you please confirm? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825632 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in linux package in Ubuntu: Confirmed Bug description: Problem when i installing the new version. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwan 3106 F pulseaudio /dev/snd/controlC1: erwan 3106 F pulseaudio Date: Sat Apr 20 12:37:44 2019 ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon InstallationDate: Installed on 2018-10-07 (194 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LB ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=d478b832-a087-4e04-824b-57099769e24e ro 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LB.603 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LB.603:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LB dmi.product.sku: ASUS-NotebookSKU 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/1825632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825698] Re: Upgrade to 19.04 from 18.10 doesnt boot
This looks to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420. Can you please confirm? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825698 Title: Upgrade to 19.04 from 18.10 doesnt boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrade completes but shows error message that linux kernel 5.0.0-13 may not be in working state. After completion of upgrade Ubuntu doesn't boot at all.. Just shows few blank screens and hangs. I reverted back to my old kernel 4.18.0-17 that was in Ubuntu 18.10 and it booted fine.. Then I dleleted the new 5.0.0-13 kernel and headers. Now Ubuntu 19.04 boots fine with old kernel. I also tried reinstalling kernel 5.0.0-13. But faced same issue again. So again I went back to old kernel. I noticed others too have been facing this problem. KINDLY LOOK INTO THE BUG AND LET US KNOW THE SOLUTION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825724] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1825420 *** https://bugs.launchpad.net/bugs/1825420 ** This bug has been marked a duplicate of bug 1825420 package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825724 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: Issue happened during upgrade of a Ubuntu server 18.10 to 19.04. Notes: lubuntu-desktop was installed on the server, and xrdp. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Apr 21 15:02:58 2019 ErrorMessage: triggers looping, abandoned IwConfig: ens18 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=ee536208-21b1-4f22-bce5-b8112499a39e ro maybe-ubiquity PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825704] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1825420 *** https://bugs.launchpad.net/bugs/1825420 ** This bug has been marked a duplicate of bug 1825420 package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825704 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 19.04, this error keeps occuring. Upgrade was not successfull. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mwoehrle 2134 F pulseaudio /dev/snd/controlC0: mwoehrle 2134 F pulseaudio /dev/snd/controlC1: mwoehrle 2134 F pulseaudio Date: Sun Apr 21 10:17:27 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=f5b7707a-0197-4446-973b-26cee2f07e80 InstallationDate: Installed on 2016-12-15 (856 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: MSI MS-7977 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=6f7d285a-3e0e-42d8-8bcc-def6e9acfe35 ro 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.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 10/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M5 (MS-7977) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd10/19/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7977 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825698] Re: Upgrade to 19.04 from 18.10 doesnt boot
Yes.. It looks like it is same problem. As the bug 1825420 referred to virtual ubuntu, I thought this requires separate reporting. You can consider this duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420 if it doesnt matter whether it is in virtual os or ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825698 Title: Upgrade to 19.04 from 18.10 doesnt boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrade completes but shows error message that linux kernel 5.0.0-13 may not be in working state. After completion of upgrade Ubuntu doesn't boot at all.. Just shows few blank screens and hangs. I reverted back to my old kernel 4.18.0-17 that was in Ubuntu 18.10 and it booted fine.. Then I dleleted the new 5.0.0-13 kernel and headers. Now Ubuntu 19.04 boots fine with old kernel. I also tried reinstalling kernel 5.0.0-13. But faced same issue again. So again I went back to old kernel. I noticed others too have been facing this problem. KINDLY LOOK INTO THE BUG AND LET US KNOW THE SOLUTION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in
I've created a wireless.conf in the /etc/modprobe.d directory with the following line: 'mt76x0u.disable_usb_sg=1'. Now the AC430 is booting right into Dongle-mode instead of USB-Storage- mode, but the error still appears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-03-31 (13 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.2-050002-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) 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.family: Virtual Machine 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-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825841] Re: Laptop battery drains while suspend since 18.04 , even in deep sleep (STR)
What kernel version have this issue and what kernel version don't have? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825841 Title: Laptop battery drains while suspend since 18.04 , even in deep sleep (STR) Status in linux package in Ubuntu: Confirmed Bug description: Hi, 1) My laptop battery drains very fast while suspend, which prevent using suspend-to-ram as I almost always find the laptop shut down due to battery being empty. I Observed this problem since my upgrade from 16.04 to 18.04 on my Laptop. It's Toshiba Portege. Suspend does work fine but battery drains while suspend; it was working pretty well in Ubuntu 16.04. I suspect a kind of regression in the i915 driver for now, but did not find any evident of this. After a suspend to ram, we can observe a kind of crash in the i915 driver suspend_late code : [ 475.970946] [ cut here ] [ 475.970947] Display power well on [ 475.971009] WARNING: CPU: 0 PID: 7579 at /build/linux-6ZmFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:8696 assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971010] Modules linked in: rfcomm ccm cmac bnep cdc_mbim uvcvideo cdc_wdm qcserial cdc_ncm usb_wwan usbserial usbnet mii btusb btrtl btbcm videobuf2_vmalloc btintel videobuf2_memops videobuf2_v4l2 videobuf2_core bluetooth videodev media ecdh_generic msr arc4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel kvm mac80211 irqbypass snd_seq intel_cstate intel_rapl_perf iwlwifi snd_seq_device snd_timer joydev cfg80211 input_leds serio_raw wmi_bmof snd rtsx_pci_ms memstick lpc_ich shpchp mei_me toshiba_acpi mei soundcore sparse_keymap toshiba_bluetooth industrialio tpm_infineon mac_hid sch_fq_codel parport_pc [ 475.971045] ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm rtsx_pci ptp pps_core video wmi [ 475.971062] CPU: 0 PID: 7579 Comm: kworker/u16:7 Not tainted 4.15.0-47-generic #50-Ubuntu [ 475.971063] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS Version 3.20 04/09/2015 [ 475.971066] Workqueue: events_unbound async_run_entry_fn [ 475.971087] RIP: 0010:assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971088] RSP: 0018:a96642bbfd00 EFLAGS: 00010286 [ 475.971089] RAX: RBX: 9bf98b0a8000 RCX: bca62768 [ 475.971090] RDX: bca62768 RSI: 0082 RDI: 0202 [ 475.971091] RBP: a96642bbfd20 R08: R09: 0015 [ 475.971091] R10: 0600 R11: 0340 R12: 9bf98b0a8358 [ 475.971092] R13: 9bf98b0a8368 R14: c0580baf R15: [ 475.971093] FS: () GS:9bf9a140() knlGS: [ 475.971094] CS: 0010 DS: ES: CR0: 80050033 [ 475.971095] CR2: 7fb1afffeeb6 CR3: 00011e20a005 CR4: 003606f0 [ 475.971096] Call Trace: [ 475.971117] hsw_enable_pc8+0x87/0x310 [i915] [ 475.971129] i915_drm_suspend_late+0xdb/0x140 [i915] [ 475.971141] i915_pm_suspend_late+0x20/0x30 [i915] [ 475.971143] pm_generic_suspend_late+0x2e/0x40 [ 475.971145] pci_pm_suspend_late+0x31/0x40 [ 475.971147] dpm_run_callback+0x5a/0x150 [ 475.971149] ? pci_pm_poweroff_late+0x40/0x40 [ 475.971151] __device_suspend_late+0xc6/0x1d0 [ 475.971152] async_suspend_late+0x1f/0xa0 [ 475.971154] async_run_entry_fn+0x3c/0x150 [ 475.971156] process_one_work+0x1de/0x410 [ 475.971158] worker_thread+0x32/0x410 [ 475.971160] kthread+0x121/0x140 [ 475.971161] ? process_one_work+0x410/0x410 [ 475.971163] ? kthread_create_worker_on_cpu+0x70/0x70 [ 475.971166] ret_from_fork+0x35/0x40 [ 475.971167] Code: d5 ff 48 8b 83 18 07 00 00 e9 b0 fd ff ff 89 ce 4c 89 f7 e8 90 fc 1a fb 0f 0b e9 99 fc ff ff 48 c7 c7 c9 0b 58 c0 e8 7d fc 1a fb <0f> 0b e9 b5 fc ff ff 48 c7 c7 7a 0c 58 c0 e8 6a fc 1a fb 0f 0b [ 475.971192] ---[ end trace 91209fe53f0c0cc2 ]--- By using a more recent kernel (4.18), I get a crash in the pc8 disable function. I am not sure whether this thread backtrace is responsible for the battery drain or not. I also read Intel open source site to help debug this, without success for now : * https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues The analyze_suspend.py script produced some bunch of data, if anyone needs
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Upgrading a cloud image, I couldn't reproduce it. I also tried installing mate-desktop-environment-core + mate-dock-applet (because it depends on bamfdaemon) before upgrading, and still couldn't reproduce. I will install a cosmic mate desktop and see if I can reproduce this problem when upgrading. However, the dpkg terminal log mentions bamfdaemon and mime-support as possible culprits on the trigger loop. So I am adding these and dpkg as well to the bug. In my opinion, this sounds more like a symptom of some trigger loop not caused by the kernel that causes dpkg to stop, which leaves the kernel unconfigured. ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New ** Also affects: mime-support (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) 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.family: Virtual Machine 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-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in
Should be "options mt76x0u disable_usb_sg=1". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-03-31 (13 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.2-050002-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Started experiencing this in Ubuntu 18.04 on two different computers, since a few days ago, presumably because of a package upgrade ; both users are using the Unity shell (if it makes any difference; I didn't try another one) ; disabling those shortcuts is important because Alt+arrow are very commonly used as Back/Forward in Chromium and Firefox, whereas the virtual console feature is almost never used and doesn't deserve more than just the usual Ctrl+Alt+Fn bindings. The dumpkeys|grep|loadkeys hack works, but the problem is that it shouldn't ever be needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
The parameters mentioned in comment 445 are working for me. Acer Aspire A315-41 (with only a internal GPU). Bios 1.11 Linux Mint 19.1 Kernel 5.1 rc Suspend/resume work. sensors command shows ~41 degree idle temp. Thx! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799791] Re: linux-kvm: please support kexec
** Changed in: linux-kvm (Ubuntu) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux-kvm (Ubuntu Cosmic) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1799791 Title: linux-kvm: please support kexec Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: Confirmed Bug description: linux-kvm doesn't support kexec. Adding support for kexec would enable other interesting uses of linux- kvm, such as for a linuxboot embedded kernel in kvm. Please enable CONFIG_KEXEC=y, CONFIG_KEXEC_FILE=y in linux-kvm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1799791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791321] Re: No video on laptop display after suspend/resume
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791321 Title: No video on laptop display after suspend/resume Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working correctly. After resume, the laptop panel remains blank with -24 (external monitors resume correctly). Suspend/resume worked correctly with -23. Ubuntu 18.04 LTS Lenovo P50 laptop, using nouveau driver --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1100 F pulseaudio /dev/snd/controlC0: john 1100 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b InstallationDate: Installed on 2017-02-01 (586 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001AUS Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET77W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001AUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN001AUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
test -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819663] Re: linux: 3.13.0-168.218 -proposed tracker
** Changed in: linux (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819663 Title: linux: 3.13.0-168.218 -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 verification-testing series: Fix Released Status in linux package in Ubuntu: Opinion Status in linux source package in Trusty: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819662 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Tuesday, 02. April 2019 10:29 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/1819663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
@Maurizio, could you test a newer Kernel? 5.1 for example to see if it's already solved, it is in my case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Hi Seth, notice only one of the stack tracks have the floppy, the mdadm one does not. I've also recreated this on a qemu q35 machine type which does not include the floppy device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip Status in linux package in Ubuntu: Confirmed Bug description: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514] schedule+0x2c/0x70 [ 967.815516] schedule_preempt_disabled+0xe/0x10 [ 967.815518] __mutex_lock.isra.10+0x2e4/0x4c0 [ 967.815522] ? exact_lock+0x11/0x20 [ 967.815524] __mutex_lock_slowpath+0x13/0x20 [ 967.815528] mutex_lock+0x2c/0x30 [ 967.815530] __blkdev_get+0x7b/0x550 [ 967.815532] ? bd_acquire+0xd0/0xd0 [ 967.815533] blkdev_get+0x10c/0x330 [ 967.815535] ? bd_acquire+0xd0/0xd0 [ 967.815537] blkdev_open+0x92/0x100 [ 967.815539] do_dentry_open+0x143/0x3a0 [ 967.815540] vfs_open+0x2d/0x30 [ 967.815542] path_openat+0x2d4/0x16d0 [ 967.815547] ? put_device+0x17/0x20 [ 967.815552] ? scsi_device_put+0x2b/0x30 [ 967.815553] do_filp_open+0x93/0x100 [ 967.81] ? strncpy_from_user+0x56/0x1b0 [ 967.815558] ? __alloc_fd+0x46/0x140 [ 967.815560] do_sys_open+0x177/0x280 [ 967.815561] ? _cond_resched+0x19/0x30 [ 967.815563] __x64_sys_openat+0x20/0x30 [ 967.815566] do_syscall_64+0x5a/0x110 [ 967.815567] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.815568] RIP: 0033:0x7faa36406cce [ 967.815572] Code: Bad RIP value. [ 967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 0101 [ 967.815574] RAX: ffda RBX: 4000 RCX: 7faa36406cce [ 967.815575] RDX: 4000 RSI: 564df70257b0 RDI: ff9c [ 967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: [ 967.815576] R10: R11: 0246 R12: 7ffedb664240 [ 967.815577] R13: R14: 0001 R15: 564df7023e00 [ 967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds. [ 967.803509] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.810235] mkfs.btrfs D0 3767 1866 0x [ 967.810239] Call Trace: [ 967.810251] __schedule+0x2d0/0x840 [ 967.810254] ? __switch_to_asm+0x34/0x70 [ 967.810256] ? __switch_to_asm+0x40/0x70 [ 967.810258] schedule+0x2c/0x70 [ 967.810260] schedule_timeout+0x258/0x360 [ 967.810277] wait_for_completion+0xb7/0x140 [ 967.810281] ? wake_up_q+0x80/0x80 [ 967.810293] __floppy_read_block_0+0x138/0x190 [floppy] [ 967.810298] ? floppy_cmos_show+0x30/0x30 [floppy] [ 967.810302] floppy_revalidate+0xf8/0x230 [floppy] [ 967.810307] check_disk_change+0x62/0x70 [ 967.810309] floppy_open+0x2ae/0x380 [floppy] [ 967.810311] __blkdev_get+0xe5/0x550 [ 967.810313] ? bd_acquire+0xd0/0xd0 [ 967.810315] blkdev_get+0x10c/0x330 [ 967.810316] ? bd_acquire+0xd0/0xd0 [ 967.810318] blkdev_open+0x92/0x100 [ 967.810321] do_dentry_open+0x143/0x3a0 [ 967.810323] vfs_open+0x2d/0x30 [ 967.810326] path_openat+0x2d4/0x16d0 [ 967.810328] ? filename_lookup.part.60+0xe0/0x170 [ 967.810332] ? strncpy_from_user+0x56/0x1b0 [ 967.810333] do_filp_open+0x93/0x100 [ 967.810353] ? strncpy_from_user+0x56/0x1b0 [ 967.810358] ? __alloc_fd+0x46/0x140 [ 967.810360] do_sys_open+0x177/0x280 [ 967.810362] ? _cond_resched+0x19/0x30 [ 967.810364] __x64_sys_openat+0x20/0x30 [ 967.810368] do_syscall_64+0x5a/0x110 [ 967.810369] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.810372] RIP: 0033:0x7f46b99374db [ 967.810377] Code: Bad RIP value. [ 967.810378] RSP: 002b:7ffc9e849d70 EFLAGS: 0246 ORIG_RAX: 0101 [
[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)
** Tags removed: targetmilestone-inin18043
** Tags added: targetmilestone-inin18041
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1818645
Title:
Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during
guest boot with > 256G of memory (kernel/kvm)
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Rebooting a PowerPC VM with > 256G of memory results in a guest crash.
== Fix ==
Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate
HPTE index in xlate function").
== Regression Potential ==
Low. Fix is trivial.
== Test Case ==
Create a PowerPC VM with > 256G of memory and reboot it repeatedly.
== Original description ==
== Comment: #0 - Satheesh Rajendran - 2019-02-28
04:38:22 ==
---Problem Description---
Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory
(kernel/kvm)
Contact Information = sathe...@in.ibm.com
---uname output---
Host Kernel: 4.15.0-1016-ibm-gt
ii qemu-system-ppc1:2.11+dfsg-
1ubuntu7.8-1ibm3 ppc64el QEMU
full system emulation binaries (ppc)
ii libvirt-bin4.0.0-1ubuntu8.6
ppc64el programs for the libvirt library
Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)
Machine Type = power9 ppc64le
---Steps to Reproduce---
1. Boot a power8 compat guest with memory >256G
virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml
sosreport attached)
Guest crashes while booting
2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package:
1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov
2018 07:42:01 +0100), qemu version: 2.11.1(Debian
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name
guest=avocado-vt-vm1,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
-machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults
-chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1
-chardev pty,id=charserial0 -device
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package:
1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov
2018 07:42:01 +0100)
2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 :
OBJECT_UNREF: obj=0x76d594111710
2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0:
char device redirected to /dev/pts/3 (label charserial0)
2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus
requested (256) exceeds the recommended cpus supported by KVM (128)
2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM
(128)
2019-02-28 10:37:18.060+: shutting down, reason=crashed
2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from
pid 14056 (/usr/sbin/libvirtd)
*Additional Instructions for sathe...@in.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
== Comment: #3 - Satheesh Rajendran - 2019-02-28
04:51:45 ==
Possible Upstream fix:
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commi
[Kernel-packages] [Bug 1821378] Re: [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
https://lists.ubuntu.com/archives/kernel-team/2019-April/100261.html
--
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/1821378
Title:
[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
in Azure kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
New
Status in linux-azure source package in Cosmic:
New
Bug description:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.
The result is accessing a bogus memory address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
Hi, Joe. I'm including the patch for 4.15. Let me know if you find any issues on the test kernel. -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs
I'm downloading 64 bit new version I'll inform -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825219 Title: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs Status in linux package in Ubuntu: Incomplete Bug description: On ubuntu 16.04 settings "do anything when closing lid" is applied. Hard reset needs. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: neslihan 1863 F...m pulseaudio /dev/snd/controlC0: neslihan 1863 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947 InstallationDate: Installed on 2018-09-12 (220 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Acer TravelMate 5335 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-47-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/26/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: BA51_MV dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Intel_Mobile dmi.product.name: TravelMate 5335 dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821378] Re: [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
https://lists.ubuntu.com/archives/kernel-team/2019-April/100267.html
--
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/1821378
Title:
[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
in Azure kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
New
Status in linux-azure source package in Cosmic:
New
Bug description:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.
The result is accessing a bogus memory address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
https://lists.ubuntu.com/archives/kernel-team/2019-April/100272.html -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi Aaron,
I did:
$ sudo dpkg -i linux-{image,headers}-4.20.0-rc3+_4.20.0-rc3+-6_amd64.deb
# edit /etc/default/grub so it now reads:
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009'
modprobe.blacklist=nouveau rmi_core.debug_flags=0x7"
$ sudo update-grub
$ sudo /sbin/shutdown now
# reboot into kernel 4.20
# touchpad now more responsive - it picks up lighter and faster touches as
clicks.
# close lid to suspend. on first two wakeups, touchpad worked
# on third wakeup, touchpad didn't work. then:
$ cat /proc/interrupts | grep rmi > rmi_irq.log
# move finger around on touchpad for several seconds, even though mouse
pointer didn't move
$ cat /proc/interrupts | grep rmi >> rmi_irq.log
# rmi_irq.log is empty
$ journalctl -b 0 -k > journalctl.log
# just for curiosity, close lid again, wait 10 seconds, reopen. Still,
mousepad is unresponsive.
# Then, without warning, laptop goes into sleep mode (with lid still open. I
press the button to resume. Screen blinks about five times, and finally wakes
up. Now, mousepad works.
$ journalctl -b 0 -k > journalctl.after_blink.log
$ wc -l journalctl.*
1735 journalctl.after_blink.log
1586 journalctl.log
Have attached journalctl.after_blink.log
Thanks in advance for any information you could provide!
** Attachment added: "journalctl.after_blink.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5258047/+files/journalctl.after_blink.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
Status in linux package in Ubuntu:
Triaged
Bug description:
Ubuntu 18.04.1
Terminology in case we use different terms:
touchpad - just the rectangular touch-sensitive surface below the keyboard
(xinput lists it as Synaptics TM3288-011)
trackpoint - the red thingy built into the keyboard + 3 physical buttons
below the keyboard (trackpoint and buttons are integrated together; listed in
xinput as TPPS/2 Elan TrackPoint)
On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
enables proper S3 deep sleep state - users no longer have to patch
DSDT tables to get it. It can be enabled in the BIOS settings. In X1
carbon 6th generation models that have NFC, when laptop wakes from
suspend by opening the lid, in most cases both touchpad and trackpoint
stop working completely. They are also no longer listed when running
xinput command. Sometimes just one of them stops working, usually the
trackpoint. In some rare cases it is possible to bring them back by
using these commands:
echo -n none > /sys/devices/platform/i8042/serio1/drvctl
echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
rmmod psmouse
modprobe psmouse
These worked properly when waking up from S2Idle sleep state (had
these in a script that runs after waking the machine from suspend),
but with S3 deep sleep these rarely work and the only way to bring
back touchpad and/or trackpoint is turning off the machine and turning
it on (restart does not help).
I could not find any pattern that would show when the input devices
stop working or start working again using the commands mentioned
above. It's completely random from my perspective.
This is happening on the standard issue 4.15.0-33-generic kernel that
shipped with my Ubuntu 18.04 (with updates), as well as with newer
mainline kernels, such as the newest point versions of 4.17, 4.18 and
4.19 RC2.
This happens regardless of whether "blacklist i2c_i801" is commented
out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
Presence of TLP does not make it better, nor worse.
It appears that non-NFC models are not affected. I know at least one
Arch Linux user who has the exact same model, but without this issue.
I'm using synaptics driver (no libinput installed), he uses libinput
and doesn't have synaptics, if that information is of any use.
Libinput does not seem to help.
This forum thread also has more details from users who updated their
BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
Suspend-to/td-p/3998182/page/27
Another related thread:
https://bbs.archlinux.org/viewtopic.php?id=236367
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.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio
/dev/snd/controlC0: maciej 2651 F pulseaudio
CurrentDesktop:
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I'm on Kubuntu and it was also affected by this issue after installing the latest updates although for me it was Super+Arrow keys that change VT (rather than Alt+KEY as described in the issue). As mentioned, running: `sudo kbd_mode -s` resolved it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen
So I can confirm that this bug happens with upstream build 5.1.0-050100rc5-generic. Will attach full dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825395 Title: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70] [37270.109843] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [37270.109848] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [37270.109849] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roland 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:40:22 2019 InstallationDate: Installed on 2019-03-29 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20JGS01000 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET45W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JGS01000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET45W(1.32):bd03/11/2019:s
[Kernel-packages] [Bug 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen
Attaching dmesg showing failed thunderbolt attachment. There is a good hotplug starting with [35304.659358] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [35304.659361] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock for example, you can see that the system discovers the downstream USB controller and USB audio device that is part of the dock: [35305.406824] xhci_hcd :0b:00.0: xHCI Host Controller [35305.406831] xhci_hcd :0b:00.0: new USB bus registered, assigned bus number 3 ... [35306.102685] usb 3-1: New USB device found, idVendor=17ef, idProduct=306a, bcdDevice=28.00 [35306.102688] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [35306.102691] usb 3-1: Product: ThinkPad Thunderbolt 3 Dock USB Audio then there are a few suspend/resume cycles, and a second hotplug of the thunderbolt dock: [40222.796009] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [40222.796010] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock in this case PCI bus enumeration seems to fail: [40223.479357] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [40223.479371] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [40223.479397] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [40223.479411] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [40223.479459] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [40223.479462] pcieport :07:04.0: PCI bridge to [bus 3d-70] [40223.479470] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [40223.479475] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [40223.479476] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them ** Tags added: kernel-bug-exists-upstream ** Attachment added: "thunderbolt-failure-dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825395/+attachment/5258054/+files/thunderbolt-failure-dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825395 Title: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordi
Re: [Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
On Mon, Apr 22, 2019 at 08:20:30PM -, Ryan Harper wrote: > Hi Seth, > > notice only one of the stack tracks have the floppy, the mdadm one does > not. I've also recreated this on a qemu q35 machine type which does not > include the floppy device. I looked at the madm stack trace, and I was assuming that it occurred during the same boot as the other one. I suppose I shouldn't have, but it would make sense. mdadm appears to be blocked on a block device's bd_mutex, so the cause is probably something else that has hung while holding that mutex. The mkfs stack trace would be just the kind of thing to create the mdadm stack trace, if it were trying to open the same device. So, were those traces from a single boot or from different boots? Can you provide stack trace(s) from the q35 machine type for comparison? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip Status in linux package in Ubuntu: Confirmed Bug description: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514] schedule+0x2c/0x70 [ 967.815516] schedule_preempt_disabled+0xe/0x10 [ 967.815518] __mutex_lock.isra.10+0x2e4/0x4c0 [ 967.815522] ? exact_lock+0x11/0x20 [ 967.815524] __mutex_lock_slowpath+0x13/0x20 [ 967.815528] mutex_lock+0x2c/0x30 [ 967.815530] __blkdev_get+0x7b/0x550 [ 967.815532] ? bd_acquire+0xd0/0xd0 [ 967.815533] blkdev_get+0x10c/0x330 [ 967.815535] ? bd_acquire+0xd0/0xd0 [ 967.815537] blkdev_open+0x92/0x100 [ 967.815539] do_dentry_open+0x143/0x3a0 [ 967.815540] vfs_open+0x2d/0x30 [ 967.815542] path_openat+0x2d4/0x16d0 [ 967.815547] ? put_device+0x17/0x20 [ 967.815552] ? scsi_device_put+0x2b/0x30 [ 967.815553] do_filp_open+0x93/0x100 [ 967.81] ? strncpy_from_user+0x56/0x1b0 [ 967.815558] ? __alloc_fd+0x46/0x140 [ 967.815560] do_sys_open+0x177/0x280 [ 967.815561] ? _cond_resched+0x19/0x30 [ 967.815563] __x64_sys_openat+0x20/0x30 [ 967.815566] do_syscall_64+0x5a/0x110 [ 967.815567] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.815568] RIP: 0033:0x7faa36406cce [ 967.815572] Code: Bad RIP value. [ 967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 0101 [ 967.815574] RAX: ffda RBX: 4000 RCX: 7faa36406cce [ 967.815575] RDX: 4000 RSI: 564df70257b0 RDI: ff9c [ 967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: [ 967.815576] R10: R11: 0246 R12: 7ffedb664240 [ 967.815577] R13: R14: 0001 R15: 564df7023e00 [ 967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds. [ 967.803509] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.810235] mkfs.btrfs D0 3767 1866 0x [ 967.810239] Call Trace: [ 967.810251] __schedule+0x2d0/0x840 [ 967.810254] ? __switch_to_asm+0x34/0x70 [ 967.810256] ? __switch_to_asm+0x40/0x70 [ 967.810258] schedule+0x2c/0x70 [ 967.810260] schedule_timeout+0x258/0x360 [ 967.810277] wait_for_completion+0xb7/0x140 [ 967.810281] ? wake_up_q+0x80/0x80 [ 967.810293] __floppy_read_block_0+0x138/0x190 [floppy] [ 967.810298] ? floppy_cmos_show+0x30/0x30 [floppy] [ 967.810302] floppy_revalidate+0xf8/0x230 [floppy] [ 967.810307] check_disk_change+0x62/0x70 [ 967.810309] floppy_open+0x2ae/0x380 [floppy] [ 967.810311] __blkdev_get+0xe5/0x550 [ 967.810313] ? bd_acquire+0xd0/0xd0 [ 967.810315] blkdev_get+0x10c/0x330 [ 967.810316] ? bd_acquire+0xd0/0xd0 [ 967.810318] blkdev_open+0x92/0x100 [ 967.810321] do_dentry_open+0x143/0x3a0 [ 967.810323] vfs_open+0x2d/0x30 [ 967.810326] path_openat+0x2d4/0
[Kernel-packages] [Bug 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU
I can confirm this bug, on different hardware. My kernel bisection resulted in the same commit (thus I found this bug). I commented on https://bugzilla.kernel.org/show_bug.cgi?id=197895#c1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730069 Title: kernel 4.10 fails to boot on AMD E-350D APU Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 motherboard). This has always worked fine until the kernel was upgraded to 4.10 as part of the regular system upgrades. Since then the machine wont boot, there are no errors, the screen just stays blank. If I boot using a previous kernel (such as 4.8.0-58-generic) then it all works fine. As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have tried have failed, currently this includes: linux-image-4.10.0-30-generic linux-image-4.10.0-32-generic linux-image-4.10.0-33-generic linux-image-4.10.0-38-generic linux-image-4.13.0-16-generic --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pim1369 F pulseaudio /dev/snd/controlC0: pim1369 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18 InstallationDate: Installed on 2017-03-11 (238 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-58-generic N/A linux-backports-modules-4.8.0-58-generic N/A linux-firmware1.157.13 RfKill: Tags: xenial Uname: Linux 4.8.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E350N WIN8 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825915] [NEW] package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Public bug reported: greg@mizuno:/var/crash$ cat /proc/version_signature Ubuntu 4.18.0-13.14-generic 4.18.17 greg@mizuno:/var/crash$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Happened during upgrade from 18.10 to 19.04. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 22 14:19:36 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1 InstallationDate: Installed on 2012-02-14 (2624 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcFB: 0 VESA VGA 1 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1825915/+attachment/5258061/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825915 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: greg@mizuno:/var/crash$ cat /proc/version_signature Ubuntu 4.18.0-13.14-generic 4.18.17 greg@mizuno:/var/crash$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Happened during upgrade from 18.10 to 19.04. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 22 14:19:36 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1 InstallationDate: Installed on 2012-02-14 (2624 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcFB: 0 VESA VGA 1 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed
[Kernel-packages] [Bug 1825915] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825915 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: greg@mizuno:/var/crash$ cat /proc/version_signature Ubuntu 4.18.0-13.14-generic 4.18.17 greg@mizuno:/var/crash$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Happened during upgrade from 18.10 to 19.04. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 22 14:19:36 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1 InstallationDate: Installed on 2012-02-14 (2624 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcFB: 0 VESA VGA 1 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed ** Tags added: disco nvidia-drm.modeset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) Status in gdm3 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Lenovo ideapad 510-15IKB OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic DE: GNOME CPU: Intel Core i5-7200U @ 4x 3.1GHz GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus) UEFI boot, Secure Boot disabled. I installed the proprietary graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. Everything works as expected if lightdm is used instead of gdm3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825915] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825915 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: Confirmed Bug description: greg@mizuno:/var/crash$ cat /proc/version_signature Ubuntu 4.18.0-13.14-generic 4.18.17 greg@mizuno:/var/crash$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Happened during upgrade from 18.10 to 19.04. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Apr 22 14:19:36 2019 ErrorMessage: triggers looping, abandoned HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1 InstallationDate: Installed on 2012-02-14 (2624 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Supermicro X8DT3 ProcFB: 0 VESA VGA 1 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/mizuno-root ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-22 (0 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: 1234567890 dmi.board.name: X8DT3 dmi.board.vendor: Supermicro dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd07/09/2018:svnSupermicro:pnX8DT3:pvr1234567890:rvnSupermicro:rnX8DT3:rvr2.0:cvnSupermicro:ct17:cvr1234567890: dmi.product.family: 1234567890 dmi.product.name: X8DT3 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Changed in: console-setup (Ubuntu Bionic) Importance: Undecided => High ** Changed in: console-setup (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820832] Re: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
This bug is about Nvidia only so please discuss AMD elsewhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [nvidia] [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in Mutter: Fix Released Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825400] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: no sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 18 22:23:41 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-07-05 (651 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.13 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.13 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1825400 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825400] Re: PCI/internal sound card not detected
It appears the kernel doesn't support your sound chip :( !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Summary changed: - PCI/internal sound card not detected + PCI/internal sound card not detected [8086:2284] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825400 Title: PCI/internal sound card not detected [8086:2284] Status in linux package in Ubuntu: New Bug description: no sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 18 22:23:41 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-07-05 (651 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.13 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-418 (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 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: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://la
[Kernel-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity
Does the problem happen in Gnome Shell too? ** Summary changed: - Different touchpad sensitivity + Touchpad vertical sensitivity is much higher than horizontal sensitivity ** Summary changed: - Touchpad vertical sensitivity is much higher than horizontal sensitivity + Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in systemsettings package in Ubuntu: New Status in xserver-xorg-input-synaptics package in Ubuntu: Incomplete Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825626] [NEW] nvLock: client timed out, taking the lock
You have been subscribed to a public bug: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ubuntu -- nvLock: client timed out, taking the lock https://bugs.launchpad.net/bugs/1825626 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-418 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825400] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1825400 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825400 Title: PCI/internal sound card not detected [8086:2284] Status in linux package in Ubuntu: Incomplete Bug description: no sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 18 22:23:41 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-07-05 (651 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.13 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]
Does the problem go away if you disable wifi? ** Summary changed: - Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. + Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0] ** Tags added: a2dp ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Tags added: a2dp-skip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825639 Title: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0] Status in bluez package in Ubuntu: Incomplete Bug description: This is the same problem in https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem persists (this T430 laptop has inbuilt Bluetooth). This makes listening to music or any audio over Bluetooth almost unbearable - while it is temporarily fixed by running `pactl suspend- sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the BIOS but the problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 20 13:10:59 2019 InstallationDate: Installed on 2018-11-26 (144 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 2349G4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB9WW (2.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349G4G dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349G4G dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 24:FD:52:8C:5D:82 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:65823 acl:64 sco:0 events:9052 errors:0 TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825739] Re: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted
Did the problem start recently, or has it always been present? If the problem started recently then please try some older kernels from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825739 Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I can hear songs okay with my speaker in laptop, but when i connect headphone in to 3.5mm jack in laptop I hear songs with crackling sound. I'm dual booting with windows. My headphones works fine in windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: devin 1493 F pulseaudio /dev/snd/controlC1: devin 1493 F pulseaudio /dev/snd/pcmC1D0c: devin 1493 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 23:45:51 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.602 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.602:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LJ dmi.product.sku: ASUS-NotebookSKU 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/alsa-driver/+bug/1825739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825828] [NEW] Display is in upside-down state by default
You have been subscribed to a public bug: The default state of display is upside-down. I'm observing this issue in latest kernels(>4.19). Command "xrandr -o normal" make things normal, but rotating display welcomes unexpected behavior. Please Check, Any help is highly appreciated. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 17:13:37 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:2212] InstallationDate: Installed on 2019-04-22 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:3841 Alcor Micro Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: iBall Aer3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=6c1f9ed6-db22-4758-9fc4-7ad00307a239 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G dmi.board.asset.tag: Default string dmi.board.name: Aer3 dmi.board.vendor: iBall dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Aer3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: iBall version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug disco ubuntu -- Display is in upside-down state by default https://bugs.launchpad.net/bugs/1825828 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** No longer affects: linux-oem (Ubuntu Cosmic) ** No longer affects: linux-oem (Ubuntu Disco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Confirmed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825823] [NEW] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
You have been subscribed to a public bug: [96438.988610] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [96438.988650] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [96438.988669] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun I've noticed i915 errors in dmesg -w ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:02:21 2019 DistUpgraded: 2018-08-21 10:26:09,893 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-46-generic, x86_64: installed anbox, 1, 4.15.0-47-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (1337 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-21 (244 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX 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.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun https://bugs.launchpad.net/bugs/1825823 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825828] Re: Display is in upside-down state by default
Are you able to identify the last known kernel version where the problem did NOT occur? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Display is in upside-down state by default + [iBall Aer3] Display is in upside-down state by default -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825828 Title: [iBall Aer3] Display is in upside-down state by default Status in linux package in Ubuntu: Incomplete Bug description: The default state of display is upside-down. I'm observing this issue in latest kernels(>4.19). Command "xrandr -o normal" make things normal, but rotating display welcomes unexpected behavior. Please Check, Any help is highly appreciated. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 17:13:37 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller [8086:2212] InstallationDate: Installed on 2019-04-22 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:3841 Alcor Micro Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: iBall Aer3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=6c1f9ed6-db22-4758-9fc4-7ad00307a239 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G dmi.board.asset.tag: Default string dmi.board.name: Aer3 dmi.board.vendor: iBall dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Aer3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: iBall version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825823] Re: [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 ** Summary changed: - noticing more i915 errors in dmesg -w + [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1550779 [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825823 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: New Bug description: [96438.988610] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [96438.988650] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [96438.988669] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun I've noticed i915 errors in dmesg -w ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:02:21 2019 DistUpgraded: 2018-08-21 10:26:09,893 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-46-generic, x86_64: installed anbox, 1, 4.15.0-47-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (1337 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-21 (244 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX 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.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX: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 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568865] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun
*** This bug is a duplicate of bug 1550779 *** https://bugs.launchpad.net/bugs/1550779 ** This bug has been marked a duplicate of bug 1550779 [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568865 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Running Gnome-Shell on ubuntu 16.04 on my Dell XPS 15 9550 laptop using Intel graphics (Nvidia card turned off), I get this error in syslog when plugging in an external monitor (HDMI). Apr 11 14:28:38 miaco kernel: [ 2616.604641] [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe B FIFO underrun Meanwhile both screens flash and show corruption. Most of the time this has caused a hang that needs a hard power off to get out of, but occasionally removing the external monitor is enough to get going again and so I've been able to find this message in the logs. Note that when using Nvidia (proprietary) drivers and Unity DE I do not have this problem; so it seems to be related to the intel drivers, or possibly Gnome Shell's use of them. Happy to help if I can (would like to be able to use external monitors!) Rich ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rich 1943 F pulseaudio Date: Mon Apr 11 14:31:26 2016 InstallationDate: Installed on 2016-03-21 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=3f8391d5-e9cc-4768-8efb-8f04d340567c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 ** This bug has been marked a duplicate of bug 1550779 [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- You 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 1825821] Re: Ubuntu 16.04 : Bluetooth can't be detected by other devices
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1825821 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1825821 Title: Ubuntu 16.04 : Bluetooth can't be detected by other devices Status in bluez package in Ubuntu: Incomplete Bug description: Hi, I am running an Ubuntu 16.04 machine. I tried to start the system bluetooth through the following steps: 1. Ensured that bluetooth was unblocked through the command rfkill 2. Set bluetooth to powered on, agent on, default-agent and scan on through bluetootctl On completing these steps, Bluetooth icon shows up as active on the system, but other devices are unable to scan it and consequently not able to connect to it. This Ubuntu does not appear in the list of bluetooth devices for other devices' scan. 3. I ran systemctl status bluetooth I am getting the following errors: nvidia@tegra-ubuntu:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-04-22 15:57:21 IST; 10min ago Docs: man:bluetoothd(8) Main PID: 1087 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─1087 /usr/lib/bluetooth/bluetoothd Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Error adding Link Loss service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Current Time Service could not be registered Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: gatt-time-server: Input/output error (5) Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Not enough free handles to register service Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: Sap driver initialization failed. Apr 22 15:57:21 tegra-ubuntu bluetoothd[1087]: sap-server: Operation not permitted (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
When there is noise, please do a test: sudo hda-verb /dev/snd/hwC0D0 0x1b SET_PIN_WIDGET_CONTROL 0x0 #if the noise disappear? sudo hda-verb /dev/snd/hwC0D0 0x1b SET_PIN_WIDGET_CONTROL 0x20 #restore the original value sudo hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x0 #if the noise disappear? sudo hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x20 #restore the original value thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V 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.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** Summary changed: - [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches + [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ** Tags removed: wily ** Tags added: bionic ** Tags added: xenial ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1605782] Re: [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 ** This bug has been marked a duplicate of bug 1550779 [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1605782 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 5890.798392] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 4106 F...m pulseaudio /dev/snd/controlC0: caravena 4106 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 22 17:28:20 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (362 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.159 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1605782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821961] Re: Fix for dual Intel NVMes
Hey there, tested the proposed -48 kernel. Did 15 reboot cycles and everything started every time. Last time it succeeded approximately 90% of the time. That is whey I went to 15 this time. Seems good. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821961 Title: Fix for dual Intel NVMes Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: [Impact] SRU for LP: #1811755 doesn't really fix the issue. Only one of the two NVMe can be correctly enumerated. [Fix] There are two separate entries for the Intel NVMe device. Fix that. [Test] User confirms it works. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825400] Re: PCI/internal sound card not detected [8086:2284]
Please uninstall all audio dkms, then reboot: first, find all eom-audio-hda-* packages via "dpkg --list | grep oem- audio-hda*" then dpkg -P those-package-names reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825400 Title: PCI/internal sound card not detected [8086:2284] Status in linux package in Ubuntu: Incomplete Bug description: no sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 18 22:23:41 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-07-05 (651 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.13 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825071] Re: Super + p does not work as expected, it's defective
I am not aware of `xrandr` used for projector mode. I have no issues with setting my monitors positions and screen resolution. The issue is when I use Super + p (projector mode) to switch between the 4 mode types: - Mirror - Join - External - Built-in If `xrandr` can toggle projector mode, I am not aware of how and I could not find anything in the man. Any assistance is appreciated. Super + p does not work as intended for 18+ currently (worked for me on 14 and 16) This may be an issue with Gnome, I will try another Gnome desktop flavor to see if this is the case. May take me a day or 2 to respond as I have a heavy workload the next few weeks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl 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-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-47-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: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+subsc
[Kernel-packages] [Bug 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- 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/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Confirmed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Kernel NULL pointer dereference in mac80211_hwsim. [Fix] a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device registered This fix has been included in 4.19.9 or above. [Test Case] $ git clone https://github.com/aircrack-ng/aircrack-ng # Tested with 69a406c $ cd aircrack-ng $ grep 'sudo apt' README.md | bash $ autoreconf -i $ ./configure --with-experimental $ make check $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration # Run integration test again and check dmesg $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration Verified with VMs setup locally. [Regression Risk] Low. Move forward data structure initialization only. This patch has also been included in LTS stable kernel. Original Bug Report The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11
