[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762928 Title: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] guests on a P9 host running bionic final beta version. Contact Information = srikanth/bssrika...@in.ibm.com ---uname output--- 16.04.04 Guest running in P8compat mode: Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 18.04 guest running in P8compat mode: Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Log into P9 Ubuntu 18.04 host, take console of guest `srikanth_ubuntu160404` 2. Run TM selftests git clone --depth 1 https://github.com/torvalds/linux.git;cd linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm run_tests We will observe one of the tm tests failing, mentioned below: selftests: tm-trap test: tm_trap_test tags: git_version:c18bb39 Little-Endian machine detected. Checking if endianness flips inadvertently on trap in TM... yes! failure: tm_trap_test not ok 1..11 selftests: tm-trap [FAIL] Expected result: All tm selftests should have been pass on the P8 compat guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host kernel Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for srikanth/bssrika...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #2 - SRIKANTH AITHAL - 2018-04-10 01:32:00 == == Comment: #3 - SRIKANTH AITHAL - 2018-04-10 01:33:41 == == Comment: #4 - SRIKANTH AITHAL - 2018-04-10 01:34:02 == Please pick `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")` ie. the commit that the test was written for To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762928] [NEW] [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
You have been subscribed to a public bug: ---Problem Description--- tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] guests on a P9 host running bionic final beta version. Contact Information = srikanth/bssrika...@in.ibm.com ---uname output--- 16.04.04 Guest running in P8compat mode: Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 18.04 guest running in P8compat mode: Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Log into P9 Ubuntu 18.04 host, take console of guest `srikanth_ubuntu160404` 2. Run TM selftests git clone --depth 1 https://github.com/torvalds/linux.git;cd linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm run_tests We will observe one of the tm tests failing, mentioned below: selftests: tm-trap test: tm_trap_test tags: git_version:c18bb39 Little-Endian machine detected. Checking if endianness flips inadvertently on trap in TM... yes! failure: tm_trap_test not ok 1..11 selftests: tm-trap [FAIL] Expected result: All tm selftests should have been pass on the P8 compat guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host kernel Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for srikanth/bssrika...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #2 - SRIKANTH AITHAL - 2018-04-10 01:32:00 == == Comment: #3 - SRIKANTH AITHAL - 2018-04-10 01:33:41 == == Comment: #4 - SRIKANTH AITHAL - 2018-04-10 01:34:02 == Please pick `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")` ie. the commit that the test was written for ** Affects: ubuntu-power-systems Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-166570 severity-critical targetmilestone-inin--- -- [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest https://bugs.launchpad.net/bugs/1762928 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 1760647] Re: Unable to build lttng module on 4.4 X-KVM
Also affecting 4.15 KVM kernel: Error! Bad return status for module build on kernel: 4.15.0-1003-kvm (x86_64) ** Tags added: bionic ** Summary changed: - Unable to build lttng module on 4.4 X-KVM + Unable to build lttng module on 4.4/4.15 KVM kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760647 Title: Unable to build lttng module on 4.4/4.15 KVM kernel Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: New Bug description: Tested with the lttng module in -proposed (2.8.0-1ubuntu1~16.04.5), it looks like this is the CONFIG issue. Build log: DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1019-kvm (x86_64) Mon Apr 2 17:05:48 UTC 2018 make: Entering directory '/usr/src/linux-headers-4.4.0-1019-kvm' /var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration. Stop. Makefile:1423: recipe for target '_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.4.0-1019-kvm' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:38:25 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
I am not that brave. I will wait until it is mainlined. Carlos EcheniquePhotographer car...@echenique.com (https://link.getmailspring.com/link/1523426190.local-9f4ce629-c6e6-v1.2.1-7e744...@getmailspring.com/0?redirect=mailto%3Acarlos%40echenique.com&recipient=MTc2MjcyNUBidWdzLmxhdW5jaHBhZC5uZXQ%3D) 305-219-2433 (tel:305-219-2433) http://www.cephotographic.com (https://link.getmailspring.com/link/1523426190.local-9f4ce629-c6e6-v1.2.1-7e744...@getmailspring.com/1?redirect=http%3A%2F%2Fwww.cephotographic.com&recipient=MTc2MjcyNUBidWdzLmxhdW5jaHBhZC5uZXQ%3D) On Apr 11 2018, at 1:47 am, Kai-Heng Feng wrote: > > Please try daily kernel at [1]. I think this commit is to solve the > issue. The fix is not in mainline yet. > > commit 5a222e8494524d04cc8de63726644759e5b132f7 > Author: Andrew Chant > Date: Fri Mar 23 19:25:23 2018 -0700 > > ALSA: usb-audio: UAC2 jack detection > [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1762725 > > Title: > Linux reports Samson Meteor USB mic as an output device > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Whenever I reboot my system, pulseaudio selects my Samson Meteor USB > mic as the default output device. I have to manually select the analog > output every time. Also, the Default effect sound does not make any > noise. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 > Uname: Linux 4.15.0-13-generic x86_64 > ApportVersion: 2.20.9-0ubuntu4 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC2: guru 2355 F pulseaudio > /dev/snd/controlC1: guru 2355 F pulseaudio > /dev/snd/controlC0: guru 2355 F pulseaudio > CurrentDesktop: Budgie:GNOME > Date: Tue Apr 10 08:54:30 2018 > InstallationDate: Installed on 2018-04-07 (2 days ago) > InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 > (20180404) > SourcePackage: pulseaudio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/06/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: A.52 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) > dmi.board.vendor: MSI > dmi.board.version: 2.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 4 > dmi.chassis.vendor: MSI > dmi.chassis.version: 2.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7A37 > dmi.product.version: 2.0 > dmi.sys.vendor: MSI > --- > ApportVersion: 2.20.9-0ubuntu4 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC2: guru 2402 F pulseaudio > /dev/snd/controlC1: guru 2402 F pulseaudio > /dev/snd/controlC0: guru 2402 F pulseaudio > CurrentDesktop: Budgie:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2018-04-07 (3 days ago) > InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 > (20180404) > IwConfig: > enp30s0 no wireless extensions. > > lo no wireless extensions. > MachineType: MSI MS-7A37 > Package: linux (not installed) > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed > root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 > ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 > RelatedPackageVersions: > linux-restricted-modules-4.15.0-13-generic N/A > linux-backports-modules-4.15.0-13-generic N/A > linux-firmware 1.173 > RfKill: > 0: hci0: Bluetooth > Soft blocked: no > Hard blocked: no > Tags: bionic > Uname: Linux 4.15.0-13-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 06/06/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: A.52 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) > dmi.board.vendor: MSI > dmi.board.version: 2.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 4 > dmi.chassis.vendor: MSI > dmi.chassis.version: 2.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7A37 > dmi.product.version: 2.0 > dmi.sys.vendor: MSI > --- > ApportVersion: 2.20.9-0ubuntu4 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC2: guru 2402 F pulseaudio > /dev/snd/controlC1: guru 2402 F pulseaudio > /dev/snd/controlC0: guru 2402 F pulseaudio > CurrentDesktop: Bu
[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device
Please try daily kernel at [1]. I think this commit is to solve the issue. The fix is not in mainline yet. commit 5a222e8494524d04cc8de63726644759e5b132f7 Author: Andrew Chant Date: Fri Mar 23 19:25:23 2018 -0700 ALSA: usb-audio: UAC2 jack detection [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749207 Title: kernel is reporting Nintendo USB microphone as an output device Status in linux package in Ubuntu: Incomplete Bug description: Kernel is reporting Nintendo USB microphone as an output device.And because that alsa will use every time as a output device ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: a 1438 F pulseaudio /dev/snd/controlC0: a 1438 F pulseaudio /dev/snd/controlC1: a 1438 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 16:48:49 2018 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ApportVersion: 2.20.8-0ubuntu9 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-13 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213) Package: linux (not installed) Tags: bionic Uname: Linux 4.16.0-041600rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675327] Re: Fix line-out port noise on Baytrail-I with RT5660 based sound card
** Also affects: linux (Ubuntu Bionic) Importance: Critical Assignee: Shrirang Bagul (shrirang-bagul) Status: Fix Released ** Also affects: linux-oem (Ubuntu Bionic) Importance: Critical Assignee: Shrirang Bagul (shrirang-bagul) Status: 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/1675327 Title: Fix line-out port noise on Baytrail-I with RT5660 based sound card Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Confirmed Bug description: On Dell IoT gateways, Baytrail-I ASoC with RT5660(ALC3277) codec supports line-out port. However, the audio output has background noise. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1675327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
Please try daily kernel at [1]. I think this commit is to solve the issue. The fix is not in mainline yet. commit 5a222e8494524d04cc8de63726644759e5b132f7 Author: Andrew Chant Date: Fri Mar 23 19:25:23 2018 -0700 ALSA: usb-audio: UAC2 jack detection [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Confirmed Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6
[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759511 Title: Fix an issue that when system in S3, USB keyboard can't wake up the system. Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# wakeup event, so USB device can't wake the system. [Test] Intel NUC can't be waken up by USB keyboard when the system is in S3. With the patch, USB keyboard can wake up the system. [Regression Potential] Low. The issue starts appearing from Gemini Lake, older generation hardware shouldn't get affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure
The default kernel for 17.10 is 4.13 based, the default kernel for 18.04 is 4.15 based. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758384 Title: [Acer AO532h] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd 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.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Acer AO532h] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO532h dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.family: Intel_Mobile dmi.product.name: AO532h dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1761443 Title: linux-aws: 4.4.0-1055.64 -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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam
I am not familiar in this area, but why does VLC work but not other Apps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708922 Title: uvcvideo module does not work with Dell XPS 12 webcam Status in ffmpeg package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: uvcvideo: Found UVC 1.00 device Integrated Webcam (0bda:5716) from Dell XPS 12 laptop (9Q33 version) does not work properly for several versions of the kernel now. guvcview nor cheese both show the issue, so it's the uvcvideo driver. Starting at 640x480 and higher resolutions, parts of lower half of video flickers / don't show image. Error messages: V4L2_CORE: (jpeg decoder) error while decoding frame V4L2_CORE: (jpeg decoder) Ignoring empty buffer V4L2_CORE: Error - Couldn't decode frame VLC seems to use another driver AND DOES NOT SHOW issue. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cheese 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 6 12:15:28 2017 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2017-04-01 (127 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331) MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: cheese ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.24.0-0ubuntu1 cheese-common 3.24.0-0ubuntu1 Signal: 8 SourcePackage: linux StacktraceTop: cheese_camera_play () from /usr/lib/x86_64-linux-gnu/libcheese.so.8 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: cheese crashed with SIGFPE in cheese_camera_play() UpgradeStatus: Upgraded to artful on 2017-06-08 (59 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1708922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic
Martin, I can confirm the issue. It's a regression introduced by LP: #1730550. Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 can solve the issue for me, please verify if it also fixes issue for you. I built an Artful kernel with the commit: https://people.canonical.com/~khfeng/lp1762693/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762693 Title: No network with e1000e driver on 4.13.0-38-generic Status in linux package in Ubuntu: Incomplete Bug description: When my computer boots with the most recent kernel 4.13.0-38-generic, I don't have a working network connection. ethtool reports that my network interface doesn't have a connection: martin@dogmeat ~ % cat ethtool.txt Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 2 Transceiver: internal Auto-negotiation: on MDI-X: Unknown (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: no dmesg contains suspicious e1000e error messages: martin@dogmeat ~ % tail -n 40 dmesg.txt [ 20.211715] Could not find valid key in user session keyring for sig specified in mount option: [459a10809c211381] [ 20.211716] One or more global auth toks could not properly register; rc = [-2] [ 20.211717] Error parsing options; rc = [-2] [ 25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 51.244686] ahci :00:17.0: port does not support device sleep [ 56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 115.022823] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 120.910537] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 125.019509] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 131.164741] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 136.039268] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 142.186891] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 147.038361] e1000e :00:1f.6 eth0: changing MTU
kernel-packages@lists.launchpad.net
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762913 Title: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(®ion->free_list_lock) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Application Cdeadmin - 2018-04-03 05:20:56 == == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 == --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT --- The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of commits need to be backported as suggested by Nick piggin. == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 == which is >>> From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001 From: Nicholas Piggin Date: Wed, 17 Jan 2018 22:47:22 +1000 Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace The powerpc NMI IPIs may not be recoverable if they are taken in some sections of code, and also there have been and still are issues with taking NMIs (in KVM guest code, in firmware, etc) which makes them a bit dangerous to use. Generic code like softlockup detector and rcu stall detectors really hammer on trigger_*_backtrace, which has lead to further problems because we've implemented it with the NMI. So stop providing NMI backtraces for now. Importantly, the powerpc code uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the softlockup and rcu hang detection traces are not being printed because the CPU is stuck with interrupts off, then the hard lockup watchdog should get it with the NMI IPI. Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup watchdog") Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/nmi.h | 4 arch/powerpc/kernel/watchdog.c | 22 -- 2 files changed, 26 deletions(-) diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h index e97f586..9c80939 100644 --- a/arch/powerpc/include/asm/nmi.h +++ b/arch/powerpc/include/asm/nmi.h @@ -4,10 +4,6 @@ #ifdef CONFIG_PPC_WATCHDOG extern void arch_touch_nmi_watchdog(void); -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask, -bool exclude_self); -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace - #else static inline void arch_touch_nmi_watchdog(void) {} #endif diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c index 87da80c..3963baa 100644 --- a/arch/powerpc/kernel/watchdog.c +++ b/arch/powerpc/kernel/watchdog.c @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void) } return 0; } - -static void handle_backtrace_ipi(struct pt_regs *regs) -{ - nmi_cpu_backtrace(regs); -} - -static void raise_backtrace_ipi(cpumask_t *mask) -{ - unsigned int cpu; - - for_each_cpu(cpu, mask) { - if (cpu == smp_processor_id()) - handle_backtrace_ipi(NULL); - else - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100); - } -} - -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self) -{ - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); -} -- 2.7.4 >>> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762913] upstream patch
Default Comment by Bridge ** Attachment added: "upstream patch" https://bugs.launchpad.net/bugs/1762913/+attachment/5110140/+files/0001-powerpc-watchdog-remove-arch_trigger_cpumask_backtra.patch ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762913 Title: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(®ion->free_list_lock) Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Application Cdeadmin - 2018-04-03 05:20:56 == == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 == --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT --- The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of commits need to be backported as suggested by Nick piggin. == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 == which is >>> From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001 From: Nicholas Piggin Date: Wed, 17 Jan 2018 22:47:22 +1000 Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace The powerpc NMI IPIs may not be recoverable if they are taken in some sections of code, and also there have been and still are issues with taking NMIs (in KVM guest code, in firmware, etc) which makes them a bit dangerous to use. Generic code like softlockup detector and rcu stall detectors really hammer on trigger_*_backtrace, which has lead to further problems because we've implemented it with the NMI. So stop providing NMI backtraces for now. Importantly, the powerpc code uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the softlockup and rcu hang detection traces are not being printed because the CPU is stuck with interrupts off, then the hard lockup watchdog should get it with the NMI IPI. Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup watchdog") Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/nmi.h | 4 arch/powerpc/kernel/watchdog.c | 22 -- 2 files changed, 26 deletions(-) diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h index e97f586..9c80939 100644 --- a/arch/powerpc/include/asm/nmi.h +++ b/arch/powerpc/include/asm/nmi.h @@ -4,10 +4,6 @@ #ifdef CONFIG_PPC_WATCHDOG extern void arch_touch_nmi_watchdog(void); -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask, -bool exclude_self); -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace - #else static inline void arch_touch_nmi_watchdog(void) {} #endif diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c index 87da80c..3963baa 100644 --- a/arch/powerpc/kernel/watchdog.c +++ b/arch/powerpc/kernel/watchdog.c @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void) } return 0; } - -static void handle_backtrace_ipi(struct pt_regs *regs) -{ - nmi_cpu_backtrace(regs); -} - -static void raise_backtrace_ipi(cpumask_t *mask) -{ - unsigned int cpu; - - for_each_cpu(cpu, mask) { - if (cpu == smp_processor_id()) - handle_backtrace_ipi(NULL); - else - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100); - } -} - -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self) -{ - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); -} -- 2.7.4 >>> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
kernel-packages@lists.launchpad.net
You have been subscribed to a public bug: == Comment: #0 - Application Cdeadmin - 2018-04-03 05:20:56 == == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 == --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT --- The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of commits need to be backported as suggested by Nick piggin. == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 == which is >>> >From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001 From: Nicholas Piggin Date: Wed, 17 Jan 2018 22:47:22 +1000 Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace The powerpc NMI IPIs may not be recoverable if they are taken in some sections of code, and also there have been and still are issues with taking NMIs (in KVM guest code, in firmware, etc) which makes them a bit dangerous to use. Generic code like softlockup detector and rcu stall detectors really hammer on trigger_*_backtrace, which has lead to further problems because we've implemented it with the NMI. So stop providing NMI backtraces for now. Importantly, the powerpc code uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the softlockup and rcu hang detection traces are not being printed because the CPU is stuck with interrupts off, then the hard lockup watchdog should get it with the NMI IPI. Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup watchdog") Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/nmi.h | 4 arch/powerpc/kernel/watchdog.c | 22 -- 2 files changed, 26 deletions(-) diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h index e97f586..9c80939 100644 --- a/arch/powerpc/include/asm/nmi.h +++ b/arch/powerpc/include/asm/nmi.h @@ -4,10 +4,6 @@ #ifdef CONFIG_PPC_WATCHDOG extern void arch_touch_nmi_watchdog(void); -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask, - bool exclude_self); -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace - #else static inline void arch_touch_nmi_watchdog(void) {} #endif diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c index 87da80c..3963baa 100644 --- a/arch/powerpc/kernel/watchdog.c +++ b/arch/powerpc/kernel/watchdog.c @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void) } return 0; } - -static void handle_backtrace_ipi(struct pt_regs *regs) -{ - nmi_cpu_backtrace(regs); -} - -static void raise_backtrace_ipi(cpumask_t *mask) -{ - unsigned int cpu; - - for_each_cpu(cpu, mask) { - if (cpu == smp_processor_id()) - handle_backtrace_ipi(NULL); - else - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100); - } -} - -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self) -{ - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); -} -- 2.7.4 >>> ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-166371 severity-high targetmilestone-inin1804 -- [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(®ion->free_list_lock) https://bugs.launchpad.net/bugs/1762913 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 1760660] Re: Unable to start docker application with KVM kernel
Hello Kamal, Yes the docker installation works fine with linux-kvm 4.4.0-1021, I will just close this bug with fix-released. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-kvm (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/1760660 Title: Unable to start docker application with KVM kernel Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Bug description: When trying to install the docker.io package on 4.4 X-kvm kenrel, it will failed with: 17:34:16 DEBUG| Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ... 17:34:16 DEBUG| addgroup: The group `docker' already exists as a system group. Exiting. 17:34:16 DEBUG| Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. 17:34:16 DEBUG| invoke-rc.d: initscript docker, action "start" failed. 17:34:16 DEBUG| ● docker.service - Docker Application Container Engine 17:34:16 DEBUG|Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) 17:34:16 DEBUG|Active: failed (Result: exit-code) since Mon 2018-04-02 17:34:15 UTC; 11ms ago 17:34:16 DEBUG| Docs: https://docs.docker.com 17:34:16 DEBUG| Process: 2991 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) 17:34:16 DEBUG| Main PID: 2991 (code=exited, status=1/FAILURE) 17:34:16 DEBUG| 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.542770021Z" ...t" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543167017Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543537340Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543915385Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.544340510Z" ...d" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: Error starting daemon: Devices cgroup ...ed 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Main process exited, code...RE 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: Failed to start Docker Application Contai...e. 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Unit entered failed state. 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Failed with result 'exit-...'. 17:34:16 DEBUG| Hint: Some lines were ellipsized, use -l to show in full. 17:34:16 DEBUG| dpkg: error processing package docker.io (--configure): 17:34:16 DEBUG| subprocess installed post-installation script returned error exit status 1 17:34:16 DEBUG| Errors were encountered while processing: 17:34:16 DEBUG| docker.io 17:34:16 DEBUG| stderr: 17:34:16 DEBUG| W: --force-yes is deprecated, use one of the options starting with --allow instead. 17:34:16 DEBUG| E: Sub-process /usr/bin/dpkg returned an error code (1) 17:34:16 INFO | ERROR ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1522690456localtime=Apr 02 17:34:16 Command failed, rc=100, Command returned non-zero exit status If this is not supported, we can blacklist this test. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 17:34:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747750] Re: [LENOVO 20KSCTO1WW] hibernate/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747750 Title: [LENOVO 20KSCTO1WW] hibernate/resume failure Status in linux package in Ubuntu: Expired Bug description: 1) cat /proc/version_signature > version.log Ubuntu 4.13.0-32.35-generic 4.13.13 ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sebastiaan 1210 F pulseaudio Date: Tue Feb 6 17:45:30 2018 DuplicateSignature: hibernate/resume:LENOVO 20KSCTO1WW:R0PET35W (1.12 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=/dev/mapper/cryptswap1 InstallationDate: Installed on 2018-02-05 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180205) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KSCTO1WW ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=ee28579a-944e-4e9a-81fe-25ecb8b0e802 ro resume=/dev/mapper/cryptswap1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux Title: [LENOVO 20KSCTO1WW] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET35W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0PET35W(1.12):bd01/22/2018:svnLENOVO:pn20KSCTO1WW:pvrThinkPadE580:rvnLENOVO:rn20KSCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E580 dmi.product.name: 20KSCTO1WW dmi.product.version: ThinkPad E580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
Can you test again on a third system? Can this be a hw problem on the first system? ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g ** Changed in: ubuntu-power-systems Status: Triaged => 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/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: New Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40
[Kernel-packages] [Bug 1654838] Re: usbipd in latest usbip package expects outdated modules
** Tags removed: 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/1654838 Title: usbipd in latest usbip package expects outdated modules Status in linux package in Ubuntu: Confirmed Bug description: It looks like the usbip package is very outdated and expects old kernel modules: root@ubuntu64:~# lsmod | grep usbip usbip_host 28672 0 usbip_core 36864 1 usbip_host root@ubuntu64:~# usbipd -D usbip err: stub_driver.c: 33 (open_sysfs_stub_driver) usbip_common_mod.ko and usbip.ko must be loaded ** (process:6599): ERROR **: driver open failed Trace/breakpoint trap (core dumped) root@ubuntu64:~# See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/comments/10 root@ubuntu64:~# lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 root@ubuntu64:~# apt-cache policy usbip usbip: Installed: 0.1.7-3 Candidate: 0.1.7-3 Version table: *** 0.1.7-3 500 500 http://za.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status I expected usbipd -D to run without errors. usbipd crashed with an error about not being able to find outdated usbip kernel modules. strace outputs this right before the error message: lstat("/sys/bus/usb/drivers/usbip", 0x7fff1240bb40) = -1 ENOENT (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: usbip 0.1.7-3 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Jan 8 13:41:09 2017 InstallationDate: Installed on 2017-01-08 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: usbip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] 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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Confirmed Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-gener
[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
** 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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: New Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware
[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
Oops, didn't see Daniel already triaged this. ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: pulseaudio (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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restr
[Kernel-packages] [Bug 1762725] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110023/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110021/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A l
[Kernel-packages] [Bug 1762725] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110019/+files/WifiSyslog.txt ** Description changed: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI + --- + ApportVersion: 2.20.9-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: guru 2402 F pulseaudio + /dev/snd/controlC1: guru 2402 F pulseaudio + /dev/snd/controlC0: guru 2402 F pulseaudio + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-07 (3 days ago) + InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) + IwConfig: + enp30s0 no wireless extensions. + + lono wireless extensions. + MachineType: MSI MS-7A37 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-13-generic N/A + linux-backports-modules-4.15.0-13-generic N/A + linux-firmware 1.173 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 4.15.0-13-generic x86_64 + UpgradeStatus: No u
[Kernel-packages] [Bug 1762725] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110027/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1762725] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110030/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-gener
[Kernel-packages] [Bug 1762725] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110020/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic
[Kernel-packages] [Bug 1762725] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110018/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110022/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13
[Kernel-packages] [Bug 1762725] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110032/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-gen
[Kernel-packages] [Bug 1762725] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110028/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.
[Kernel-packages] [Bug 1762725] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110031/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110025/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1762725] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110024/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110026/+files/ProcCpuinfoMinimal.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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modul
[Kernel-packages] [Bug 1762725] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110029/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)
4.13.0-38-generic #43~lp1745646ThreeRevert fixed the bug . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 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.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755954] Re: external mic not work on Dell OptiPlex 7460 AIO
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755954 Title: external mic not work on Dell OptiPlex 7460 AIO Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: == SRU Justification == We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't detect external mic and can't record sound via external mic. After applying the fixup of ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, the problem can be fixed. == Fix == 40e2c4e5("iALSA: hda/realtek - Add headset mode support for Dell laptop") == Regression Potential == very low, since this patch only applies to specific Dell machines which have subsystem id: 1028084b and 1028084e. == Test Case == plug the headset and record the sound on this machine, we can see the external mic in the sound-setting and can record sound through this mic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1755954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759088] Re: can't record sound via front headset port on the Dell Precision 3630
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759088 Title: can't record sound via front headset port on the Dell Precision 3630 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: [Impact] The Dell Precision 3630 is a desktop computer, it has only one front headset jack on it, after we plug a headset in it, we can't record sound via the headset-mic. And Realtek told us that "This platform was the fixed type headset only for iphone type. Fixed type headset was not run for default headset mode rule. It's hardware fixed type solution. Don't need to run software headset mode. Hardware layout not support UAJ functions." And Realtek submitted this patch to fix this problem. [Fix] With this patch, the driver only set pin 0x19 as the headset-mic and will not call alcxxx_headset_mode init function anymore since the circuit is hardware fixed to be iphone-type headset-mic. [Test Case] Boot up the system, and plug a iphone-type headset, record the sound via headset-mic, it can record the sound and sound quality is pretty good. [Regression Potential] Very low, this patch is only specific to precision 3930 (subsystem id: 0x10280871 and 0x10280872). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110009/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13
[Kernel-packages] [Bug 1762725] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110013/+files/ProcCpuinfoMinimal.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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modul
[Kernel-packages] [Bug 1762725] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110017/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-gener
[Kernel-packages] [Bug 1762725] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110012/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1762725] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110011/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110015/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.
[Kernel-packages] [Bug 1762725] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110010/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A
[Kernel-packages] [Bug 1762725] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110014/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1762725] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110016/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-g
[Kernel-packages] [Bug 1762725] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110008/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2402 F pulseaudio /dev/snd/controlC1: guru 2402 F pulseaudio /dev/snd/controlC0: guru 2402 F pulseaudio CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-07 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IwConfig: enp30s0 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7A37 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A l
[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device
apport information ** Tags added: apport-collected ** Description changed: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI + --- + ApportVersion: 2.20.9-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: guru 2402 F pulseaudio + /dev/snd/controlC1: guru 2402 F pulseaudio + /dev/snd/controlC0: guru 2402 F pulseaudio + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-07 (3 days ago) + InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) + IwConfig: + enp30s0 no wireless extensions. + + lono wireless extensions. + MachineType: MSI MS-7A37 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-13-generic N/A + linux-backports-modules-4.15.0-13-generic N/A + linux-firmware 1.173 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 4.15.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/06/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: A.52 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) + dmi.board.vendor: MSI + dmi.board.version: 2.0 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 4 + dmi.chassis.vendor: MSI + dmi.chassis.version: 2.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: MS-7A37 + dmi.product.version: 2.0 + dmi.sys.vendor: MSI ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1762725/+attachment/5110007/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64
[Kernel-packages] [Bug 1762604] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1724863 *** https://bugs.launchpad.net/bugs/1724863 You will unfortunately need to update your machine using ethernet or a USB network device to get the required fix... Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1724863, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1724863 bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 [error: ‘struct net_device’ has no member named ‘last_rx’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1762604 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: After update of linux kernel to 4.13.0-38.generic, my wireless wifi is not working anymore. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.13.0-38-generic Date: Wed Apr 4 18:13:31 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ InstallationDate: Installed on 2017-04-21 (353 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1762604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] 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 1762725 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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: Incomplete Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device
Incomplete regarding comment #8. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749207 Title: kernel is reporting Nintendo USB microphone as an output device Status in linux package in Ubuntu: Incomplete Bug description: Kernel is reporting Nintendo USB microphone as an output device.And because that alsa will use every time as a output device ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: a 1438 F pulseaudio /dev/snd/controlC0: a 1438 F pulseaudio /dev/snd/controlC1: a 1438 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 16:48:49 2018 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ApportVersion: 2.20.8-0ubuntu9 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-13 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213) Package: linux (not installed) Tags: bionic Uname: Linux 4.16.0-041600rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] Re: Ubuntu Budgie selects USB mic as default audio output after every reboot.
PulseAudio is selecting the USB device for output because that's correct behaviour for USB speakers. And PulseAudio thinks the mic is a speaker because that's what ALSA seems to be telling it. The real problem here is that the Linux kernel seems to be reporting the mic is an output device. Much like bug 1749207. ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Summary changed: - Ubuntu Budgie selects USB mic as default audio output after every reboot. + Linux reports Samson Meteor USB mic as an output 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/1762725 Title: Linux reports Samson Meteor USB mic as an output device Status in linux package in Ubuntu: New Bug description: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device
See also bug 1762725 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749207 Title: kernel is reporting Nintendo USB microphone as an output device Status in linux package in Ubuntu: Incomplete Bug description: Kernel is reporting Nintendo USB microphone as an output device.And because that alsa will use every time as a output device ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: a 1438 F pulseaudio /dev/snd/controlC0: a 1438 F pulseaudio /dev/snd/controlC1: a 1438 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 16:48:49 2018 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212) IwConfig: lono wireless extensions. enp1s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ApportVersion: 2.20.8-0ubuntu9 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-02-13 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213) Package: linux (not installed) Tags: bionic Uname: Linux 4.16.0-041600rc1-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762725] [NEW] Ubuntu Budgie selects USB mic as default audio output after every reboot.
You have been subscribed to a public bug: Whenever I reboot my system, pulseaudio selects my Samson Meteor USB mic as the default output device. I have to manually select the analog output every time. Also, the Default effect sound does not make any noise. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: guru 2355 F pulseaudio /dev/snd/controlC1: guru 2355 F pulseaudio /dev/snd/controlC0: guru 2355 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Apr 10 08:54:30 2018 InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.52 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350M MORTAR ARCTIC (MS-7A37) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A37 dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Ubuntu Budgie selects USB mic as default audio output after every reboot. https://bugs.launchpad.net/bugs/1762725 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 1759961] Re: Update to 5.49 (mostly bug-fix release)
We also discussed 5.49 at the last Bluetooth meeting, and came to the same conclusion. -- 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/1759961 Title: Update to 5.49 (mostly bug-fix release) Status in bluez package in Ubuntu: Triaged Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)
I think we're waiting for version 5.50 or later (for bug 1759628). And even if that was available today we'd still not introduce it till 18.10. I'd like to keep bluez and pulseaudio in a maturing state, which means they haven't changed in a long time when 18.04 is released. -- 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/1759961 Title: Update to 5.49 (mostly bug-fix release) Status in bluez package in Ubuntu: Triaged Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)
Oh it looks like bug 1759628 is fixed in v5.49, but still, same plan. ** Summary changed: - Update to 5.49 in Bionic (mostly bug-fix release) + Update to 5.49 (mostly bug-fix release) -- 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/1759961 Title: Update to 5.49 (mostly bug-fix release) Status in bluez package in Ubuntu: Triaged Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Finally got a machine up and running. Will resume testing shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2018-04-10 21:32 EDT--- According to test they have another bostonLC (boslcp4) and they did update to this kernel and system is booting up normally. root@boslcp4:~# uname -a Linux boslcp4 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# date Tue Apr 10 16:37:37 CDT 2018 root@boslcp4:~# uptime 16:37:38 up 40 min, 2 users, load average: 0.00, 0.03, 0.12 Additionally, I rebooted the system a third time to add the slub_debug=FZ kernel option and system booted to the login and I logged in successfully. I did it a fourth time and it succeeded again. root@boslcp3:~# uname -a Linux boslcp3 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# cat /proc/cmdline root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro xmon=on splash quiet slub_debug=FZ Strange. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in linux package in Ubuntu: New Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R3
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Hi Imperia, I built a mainline kernel (version 4.16) with a different quirk that I think might help here. Can you test it? Thanks in advance! Instructions (run all as root): 1) wget people.canonical.com/~gpiccoli/imperia416.tgz 2) mv imperia416.tgz / 3) tar -zxf imperia416.tgz 4) update-initramfs -c -k 4.16.0-imperia+ Now that's important: if you have access to some serial console in the machine (or if you have physical access), you can reboot into this new kernel. In case _you only have ssh_, I'd suggest to remove the kernel boot entry from grub, and boot through kexec for safety reasons: a) Remove boot entries from grub.cfg (you can copy away vmlinuz-4.16-imperia+ to some place outside /boot and run "update-grub" for this) b) apt-get install kexec-tools c) kexec vmlinuz-4.16-imperia+ --initrd initrd.img-4.16-imperia+ --append="$(cat /proc/cmdline)" After machine (hopefully!) boot to the new kernel, check in dmesg if the quirk is there: #$ dmesg|grep QUIRK [0.813486] QUIRK: XHCI_AVOID_BEI If you can see that output ("QUIRK: XHCI_AVOID_BEI"), then the quirk was applied. Now, just need to try to reproduce the issue again. Thanks a lot, 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux package in Debian: New Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
On Tue, Apr 10, 2018 at 05:12:22AM -, Mario Limonciello wrote: > > Did I get the interpretation of these rules correct? > At a glance it looks like what you thought, but dig a little deeper. > If it's not in the ACL it exits. Ah! Thanks Mario! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunde
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
Not yet -- 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/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
Is there a kernel ready for testing this on bionic or xenial? -- 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/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux F
[Kernel-packages] [Bug 1762844] boslcp3 host console logs_4.15.0-15 kernel
Default Comment by Bridge ** Attachment added: "boslcp3 host console logs_4.15.0-15 kernel" https://bugs.launchpad.net/bugs/1762844/+attachment/5109823/+files/boslcp3_hostconsolelogs_4.15.0-15kernel.txt ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel Status in linux package in Ubuntu: New Bug description: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c allo
[Kernel-packages] [Bug 1758384] Re: [Acer AO532h] hibernate/resume failure
Which kernel should I use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758384 Title: [Acer AO532h] hibernate/resume failure Status in linux package in Ubuntu: Incomplete Bug description: I put the computer in hibernation using sudo pm-hibernate. Computer seemed to go into hibernation normally but didn't wake up properly. System hibernates properly under Artful. Disk has a proper 2gb swap partition. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 [modified: boot/vmlinuz-4.15.0-12-generic] ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ka1ssr 1005 F pulseaudio Date: Fri Mar 23 12:36:52 2018 DuplicateSignature: hibernate/resume:Acer AO532h:V1.26 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=600f4807-bc16-448c-9a8f-bf5330a75d9e InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323) InterpreterPath: /usr/bin/python3.6 MachineType: Acer AO532h ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=d2c54fce-ed1a-4448-b75b-94fad1b35afd 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.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux Title: [Acer AO532h] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/28/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO532h dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnAcer:bvrV1.26:bd04/28/2011:svnAcer:pnAO532h:pvrV1.26:rvnAcer:rnAO532h:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.family: Intel_Mobile dmi.product.name: AO532h dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762844] [NEW] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel
You have been subscribed to a public bug: Problem Description: === Host crashed & enters into xmon after updating to 4.15.0-15.16 kernel kernel. Steps to re-create: == 1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels 2. Installed boslcp3 with latest kernel 4.15.0-13-generic 3. Enabled "-proposed" kernel in /etc/apt/sources.list file 4. Ran sudo apt-get update & apt-get upgrade 5. root@boslcp3:~# ls /boot abi-4.15.0-13-generic retpoline-4.15.0-13-generic abi-4.15.0-15-generic retpoline-4.15.0-15-generic config-4.15.0-13-generic System.map-4.15.0-13-generic config-4.15.0-15-generic System.map-4.15.0-15-generic grub vmlinux initrd.imgvmlinux-4.15.0-13-generic initrd.img-4.15.0-13-generic vmlinux-4.15.0-15-generic initrd.img-4.15.0-15-generic vmlinux.old initrd.img.old 6. Rebooted & booted with 4.15.0-15 kernel 7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub 8. Rebooted host. 9. Booted with 4.15.0-15 & provided root/password credentials in login prompt 10. Host crashed & enters into XMON state with 'Unable to handle kernel paging request' root@boslcp3:~# [ 66.295233] Unable to handle kernel paging request for data at address 0x8882f6ed90e9151a [ 66.295297] Faulting instruction address: 0xc038a110 cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650] pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350 lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350 sp: c692f8d0 msr: 90009033 dar: 8882f6ed90e9151a current = 0xc698fd00 paca= 0xcfab7000 softe: 0irq_happened: 0x01 pid = 1762, comm = systemd-journal Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 4.15.0-15.16-generic 4.15.15) enter ? for help [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0 [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c692fe30] c000b184 system_call+0x58/0x6c --- Exception: c00 (System Call) at 74826f6fa9c4 SP (75dc5510) is in userspace 50:mon> 50:mon> 10. Attached Host console logs I rebooted the host just to see if it would hit the issue again and this time I didn't even get to the login prompt but it crashed in the same location: 50:mon> r R00 = c0389fd4 R16 = c000200e0b20fdc0 R01 = c000200e0b20f8d0 R17 = 0048 R02 = c16eb400 R18 = 0001fe80 R03 = 0001 R19 = R04 = 0048ca1cff37803d R20 = R05 = 0688 R21 = R06 = 0001 R22 = 0048 R07 = 0687 R23 = 4882d6e3c8b7ab55 R08 = 48ca1cff37802b68 R24 = c000200e5851df01 R09 = R25 = 8882f6ed90e67454 R10 = R26 = c0b2ec6c R11 = c0d10f78 R27 = c00ff901ee00 R12 = 2000 R28 = R13 = cfab7000 R29 = 015004c0 R14 = c000200e4c973fc8 R30 = c000200e5851df01 R15 = c000200e4c974238 R31 = c00ff901ee00 pc = c038a110 kmem_cache_alloc_node+0x2f0/0x350 cfar= c0016e1c arch_local_irq_restore+0x1c/0x90 lr = c038a0fc kmem_cache_alloc_node+0x2dc/0x350 msr = 90009033 cr = 28002844 ctr = c061e1b0 xer = trap = 380 dar = 8882f6ed90e67454 dsisr = c000200e40bd8400 50:mon> t [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 (unreliable) [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220 [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0 [c000200e0b20fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0 [c000200e0b20fae0] c0c56ae4 unix_stream_sendmsg+0x264/0x5c0 [c000200e0b20fbc0] c0b1ec64 sock_sendmsg+0x64/0x90 [c000200e0b20fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390 [c000200e0b20fd90] c0b221ec __sys_sendmsg+0x5c/0xc0 [c000200e0b20fe30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 7d16a993a940 SP (7bee2270) is in userspace Mirroring to Canonical to advise them that this might be possible regression. Didn't see any obvious changes in this area in the changelog published at https://launchpad.net/ubuntu/+source/linux/4.15.0-15.16 but it would be good to have Canonical help reviewing the deltas as we try to isolate this further. ** Affects: linux (Ubuntu) Importa
[Kernel-packages] [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam
I don't see how this is a bug in ffmpeg. The feature request linked in this bug report is asking for a workaround for a buggy kernel driver which will not fix the underlying issue, and isn't going to fix any other programs using the webcam anyway. ** Changed in: ffmpeg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708922 Title: uvcvideo module does not work with Dell XPS 12 webcam Status in ffmpeg package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: uvcvideo: Found UVC 1.00 device Integrated Webcam (0bda:5716) from Dell XPS 12 laptop (9Q33 version) does not work properly for several versions of the kernel now. guvcview nor cheese both show the issue, so it's the uvcvideo driver. Starting at 640x480 and higher resolutions, parts of lower half of video flickers / don't show image. Error messages: V4L2_CORE: (jpeg decoder) error while decoding frame V4L2_CORE: (jpeg decoder) Ignoring empty buffer V4L2_CORE: Error - Couldn't decode frame VLC seems to use another driver AND DOES NOT SHOW issue. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cheese 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 6 12:15:28 2017 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2017-04-01 (127 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331) MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: cheese ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.24.0-0ubuntu1 cheese-common 3.24.0-0ubuntu1 Signal: 8 SourcePackage: linux StacktraceTop: cheese_camera_play () from /usr/lib/x86_64-linux-gnu/libcheese.so.8 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: cheese crashed with SIGFPE in cheese_camera_play() UpgradeStatus: Upgraded to artful on 2017-06-08 (59 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1708922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761930] Re: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic
Also tested 4.13.0-38-generic without any of the extras modules packages etc. ** Tags added: kernel-fixed-upstream ** 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/1761930 Title: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762468] Re: Cryptoswap not working in Bionic
Looks like the same issue as reported on lp:#1736072 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762468 Title: Cryptoswap not working in Bionic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have cryptoswap set up both with the 2 GB default swap file and an 8 GB swap partition with 8 GB of ram. However, the system does not use this swap when it should. For example, if I run a little test code which attempts to allocate 10 GB of memory in 1 GB chuncks, the system hangs with no obvious use of swap. E.g. running top shows no swap use before the hang. However, if I replace cryptoswap by standard swap, it works as expected: allocates the requested memory and exits, using swap. Of course, my disk is slow, so this takes some time but it does work. I originally noticed this problem when compiling a very large application. The system would hang on ld. I've checked hardware using memtest and stress. No problems. This took me days to track down but I'm 99% certain now that the problem is with cryptoswap. If I compile with cryptoswap: hang. If I compile with standard swap: no problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: weinberg 2425 F pulseaudio /dev/snd/controlC0: weinberg 2425 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 11:57:23 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR
ubuntu@foufoune:~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ubuntu@foufoune:~$ apt-cache policy systemd systemd: Installed: 234-2ubuntu12.3 Candidate: 234-2ubuntu12.3 Version table: *** 234-2ubuntu12.3 500 500 http://azure.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 234-2ubuntu12.1 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 234-2ubuntu12 500 500 http://azure.archive.ubuntu.com/ubuntu artful/main amd64 Packages ubuntu@foufoune:~$ time ping __cloud_init_expected_not_found ping: __cloud_init_expected_not_found: Temporary failure in name resolution real0m15.016s user0m0.000s sys 0m0.003s After applying the workaround from comment #11, I see fast lookups again. ubuntu@foufoune:~$ cat /etc/systemd/resolved.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See resolved.conf(5) for details [Resolve] #DNS= #FallbackDNS= #Domains= #LLMNR=yes #MulticastDNS=yes #DNSSEC=no #Cache=yes #DNSStubListener=udp LLMNR=no ubuntu@foufoune:~$ time ping __cloud_init_expected_not_found ping: __cloud_init_expected_not_found: Name or service not known real0m0.006s user0m0.000s sys 0m0.001s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in glibc source package in Artful: New Status in linux source package in Artful: New Status in systemd source package in Artful: New Status in glibc source package in Bionic: Invalid Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
big chunk of kern.log with addresses and serial numbers elided. ** Attachment added: "kern.log with some privacy filtering" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+attachment/5109724/+files/kern.log ** 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/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Confirmed Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723717] Re: Please remove from archives: usbip & usbip-source
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723717 Title: Please remove from archives: usbip & usbip-source Status in linux package in Ubuntu: Invalid Status in usbip package in Ubuntu: Fix Released Bug description: These packages have not been supported since Apr 2009, and now linux- tools-common deal with the required features. https://bugs.launchpad.net/ubuntu/utopic/+source/usbip/+bug/898003/comments/40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
Marked confirmed per auto-comment #1 but I'm happy to add other logs on request (not going to audit 11,000 lines of apport output if I can at all avoid it, though.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Confirmed Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762824] [NEW] hisi_sas: Revert and replace SAUCE patches w/ upstream
Public bug reported: We're carrying a couple SAUCE patches for the hisi_sas driver to enable hip08 SoC support. Alternative patches have since landed upstream, which are more complete, and will be a better basis for backporting future patches to this driver. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: 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/1762824 Title: hisi_sas: Revert and replace SAUCE patches w/ upstream Status in linux package in Ubuntu: In Progress Bug description: We're carrying a couple SAUCE patches for the hisi_sas driver to enable hip08 SoC support. Alternative patches have since landed upstream, which are more complete, and will be a better basis for backporting future patches to this driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762816] Re: chaoskey interferes with suspend on thinkpad
On inspection of apport-collect output, it doesn't appear to filter out serial numbers or SSIDs, so I can't submit it. Also, it seems to have left out any of the logs where the tracebacks mentioned above were included; I'll add at least a useful chunk of kern.log surrounding the problem as an attachment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
Removing the scsi_mod.use_blk_mq=1 from /etc/default/grub and the mentioned udev rule file, and regenerating initial ramdisk + reboot seems to do the trick, now everything works with default (cfq) I/O scheduler. Before this comment, and the problem: # cat /sys/block/sda/queue/scheduler [bfq] none # cat /sys/block/sdb/queue/scheduler [none] bfq After I removed the BFQ specific stuffs and everything worked again: # cat /sys/block/sda/queue/scheduler noop deadline [cfq] # cat /sys/block/sdb/queue/scheduler noop deadline [cfq] So, sorry about the noise, maybe it was my fault ... Interestingly, this setup of mine with BFQ worked in 17.10 on other machines with that kernel parameter and udev rule I mentioned in the previous comment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762450 Title: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've upgraded to 18.04. Since then, it's impossible to use thumb- drives. If I try, on the first write operation, that operation hangs. Trying to issue a 'sync' command that hangs too. After a while (some minutes or so?) I see the following in kernel log / dmesg (see later). It's not even possible to cleanly shut the computer down, as it also hangs then. kernel is: 4.15.0-15-generic Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -S /boot/vmlinuz-4.15.0-15-generic linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic $ dpkg -l linux-image-4.15.0-15-generic ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64 Linux kernel image for version 4.15.0 on 64 bit x86 SMP dmesg: [ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd [ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00 [ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.083441] usb 6-1: Product: DataTraveler 2.0 [ 111.083444] usb 6-1: Manufacturer: Kingston [ 111.083447] usb 6-1: SerialNumber: 5B7402949950 [ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected [ 111.157882] scsi host6: usb-storage 6-1:1.0 [ 111.158826] usbcore: registered new interface driver usb-storage [ 111.174387] usbcore: registered new interface driver uas [ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB) [ 112.443462] sd 6:0:0:0: [sdb] Write Protect is off [ 112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 112.443586] sd 6:0:0:0: [sdb] No Caching mode page found [ 112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk this was ok, the problem is from here: [ 363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 363.231745] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.231750] fdisk D0 1798 1728 0x [ 363.231754] Call Trace: [ 363.231764] __schedule+0x297/0x8b0 [ 363.231768] ? fdatawait_one_bdev+0x20/0x20 [ 363.231771] schedule+0x2c/0x80 [ 363.231775] io_schedule+0x16/0x40 [ 363.231779] wait_on_page_bit_common+0xd8/0x160 [ 363.231782] ? page_cache_tree_insert+0xe0/0xe0 [ 363.231785] __filemap_fdatawait_range+0xfa/0x160 [ 363.231788] ? __filemap_fdatawrite_range+0xc1/0x100 [ 363.231791] ? __filemap_fdatawrite_range+0xcd/0x100 [ 363.231794] ? __sync_filesystem+0x60/0x60 [ 363.231797] filemap_fdatawait_keep_errors+0x1e/0x40 [ 363.231799] fdatawait_one_bdev+0x16/0x20 [ 363.231802] iterate_bdevs+0xb7/0x160 [ 363.231805] sys_sync+0x7e/0xb0 [ 363.231809] do_syscall_64+0x73/0x130 [ 363.231813] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 363.231816] RIP: 0033:0x7f2fcff17287 [ 363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 00a2 [ 363.231820] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287 [ 363.231821] RDX: RSI: 56096b766018 RDI: 56096b767400 [ 363.231823] RBP: 7fffbbea82d8 R08: 000a R09: 7472617020656854 [ 363.231824] R10: 0008 R11: 0202 R12: 56096a25b198 [ 363.231825] R13: R14: 56096a25b198 R15: [ 484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 484.045934] Tainted: G
[Kernel-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR
I'm seeing this on Artful as well, in Azure cloud. ** Also affects: glibc (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in glibc source package in Artful: New Status in linux source package in Artful: New Status in systemd source package in Artful: New Status in glibc source package in Bionic: Invalid Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: When testing MAAS on Bionic, we noticed sluggish performance that we could not immediately explain. After comparing the results from a run of the test suite on Xenial to a run on Bionic, we determined that the slowdowns had to do with DNS lookups. In particular, if MAAS attempts to resolve a hostname using getaddrinfo() and the call fails, on Xenial the negative result is returned in a fraction of a second. On Bionic, the negative result is returned in ~1.6 seconds, according to some measures. ### To run the test ### git clone https://github.com/mpontillo/test-getaddrinfo cd test-getaddrinfo make ### Results on Xenial ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Success getaddrinfo() return value: -2 (Name or service not known) real 0m0.015s user 0m0.000s sys 0m0.000s ### Results on Bionic ### $ time ./test not-a-real-hostname Trying to resolve: not-a-real-hostname getaddrinfo errno: Resource temporarily unavailable getaddrinfo() return value: -3 (Temporary failure in name resolution) real 0m1.609s user 0m0.004s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762812] Re: /dev/ipmi enumeration flaky on Cavium Sabre nodes
** Description changed: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). + *** Note that systems need to be running firmware 6.2 or greater *** [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762812 Title: /dev/ipmi enumeration flaky on Cavium Sabre nodes Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). *** Note that systems need to be running firmware 6.2 or greater *** [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762816] 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 1762816 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 ** Tags added: 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/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760657] Re: test_160_setattr_CVE_2015_1350 in kernel security test failed with 4.4/4.15 kvm
** Changed in: linux-kvm (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => 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/1760657 Title: test_160_setattr_CVE_2015_1350 in kernel security test failed with 4.4/4.15 kvm Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: In Progress Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: In Progress Bug description: FAIL: test_160_setattr_CVE_2015_1350 (__main__.KernelSecurityTest) Ensure unpriv user cannot strip setattr attributes via chown() (CVE-2015-1350) -- Traceback (most recent call last): File "./test-kernel-security.py", line 1973, in test_160_setattr_CVE_2015_1350 self.assertShellExitEquals(0, ['setcap', 'cap_sys_nice+ep', testbin]) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: Got exit code 1, expected 0 Command: 'setcap', 'cap_sys_nice+ep', '/tmp/setattr-lEzy4F/true' Output: Failed to set capabilities on file `/tmp/setattr-lEzy4F/true' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 17:23:14 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1760657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760650] Re: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm
** Changed in: linux-kvm (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => 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/1760650 Title: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm Status in QA Regression Testing: New Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Xenial: In Progress Status in linux-kvm source package in Bionic: In Progress Bug description: FAIL: test_074_config_security_default_mmap_min_addr (__main__.KernelSecurityTest) CONFIG_DEFAULT_MMAP_MIN_ADDR -- Traceback (most recent call last): File "./test-kernel-security.py", line 832, in test_074_config_security_default_mmap_min_addr self.assertEqual(self._get_config(config), expected) AssertionError: '4096' != '65536' Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 17:13:02 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1760650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762816] [NEW] chaoskey interferes with suspend on thinkpad
Public bug reported: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been going on for the last month of bionic, and *possibly* longer but I only recently caught that the Chaoskey was related. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ uname -a Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg --status linux-image-4.15.0-13-generic Package: linux-image-4.15.0-13-generic Status: install ok installed Priority: optional Section: kernel Installed-Size: 72167 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.15.0-13.14 Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, zfs-dkms, zfs-modules Depends: kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, initramfs-tools | linux-initramfs-tool Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, linux-headers-4.15.0-13-generic Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP This package contains the Linux kernel image for version 4.15.0 on 64 bit x86 SMP. . Also includes the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-generic meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1762816 Title: chaoskey interferes with suspend on thinkpad Status in linux package in Ubuntu: Incomplete Bug description: Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into the docking station - suspend fails often (more than half the time, maybe not 100% but easily duplicated in my setup) in that it doesn't seem to go all the way down - and on wakeup, lsusb output doesn't update, `lsusb -t` hangs when run. It *may* require "suspend, undock, unsuspend" but I'm not convinced... Interesting logs include a "blocked for more than 120 seconds" traceback after restore that goes through chaoskey_disconnect even though the laptop is undocked so it's no longer attached: [17038.103142] Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 schedule_timeout+0x1cf/0x350 ? ttwu_do_activate+0x7a/0x90 wait_for_completion+0xba/0x140 ? wake_up_q+0x80/0x80 hwrng_unregister+0x8f/0xa0 *** chaoskey_disconnect+0xbe/0x110 [chaoskey] *** usb_unbind_interface+0x77/0x290 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 device_del+0x13d/0x360 ? usb_remove_ep_devs+0x1f/0x30 usb_disable_device+0x9f/0x270 usb_disconnect+0xc6/0x270 hub_quiesce+0x48/0xa0 hub_event+0xfb/0xb10 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ? do_syscall_64+0x73/0x130 ? SyS_exit_group+0x14/0x20 ret_from_fork+0x35/0x40 Kernel is most recently `4.15.0-13-gene
[Kernel-packages] [Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1566468 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux-kvm source package in Xenial: New Status in linux-raspi2 source package in Xenial: Confirmed Status in open-iscsi source package in Xenial: Invalid Bug description: On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time: systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Load Kernel Modules. systemd[1]: systemd-modules-load.service: Unit entered failed state. systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. The following related complaint appears in /var/log/syslog: ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp' ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser' It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg. More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd- modules-load-service-failed-due-to-missing-module-ib-i --- root@testvm4:~# lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@testvm4:~# apt policy systemd systemd: Installed: 229-3ubuntu2 Candidate: 229-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1710517] Re: Enable EFI stub for raspi2 kernels
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1710517 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710517 Title: Enable EFI stub for raspi2 kernels Status in linux package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: New Bug description: U-boot is now able to emulate UEFI and this is used by openSUSE to boot the raspberry pi [1]. I would like to use this technique to load grub2. However, according to [2] new versions of grub2 require a 32 bit kernel to be built with EFI stub enabled. I have successfully used this U-boot/grub2 combination to boot a generic aarch64 Ubuntu kernel on my pi3 [3]. It works well and would be a huge improvement if this could be brought to arm 32 bit. [1] https://www.suse.com/docrep/documents/a1f0ledpbe/UEFI%20on%20Top%20of %20U-Boot.pdf [2] https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB [3] https://lists.ubuntu.com/archives/lubuntu- users/2017-August/011613.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)
Linux gopal-HP-Notebook 4.13.0-38-generic #43~lp1745646ThreeReverts SMP Tue Apr 10 15:04:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux http://paste.ubuntu.com/p/RkbKWgWsCs/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 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.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762812] [NEW] /dev/ipmi enumeration flaky on Cavium Sabre nodes
Public bug reported: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Artful) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Description changed: - There are several stability issues with the i2c-xlp9xxx that cause - communication issues between the host and the BMC, leading to - unpredictable results when the ipmi-ssif module tries to enumerate the - device. + [Impact] + There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). + + [Test Case] + Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). + + [Regression Risk] + All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762812 Title: /dev/ipmi enumeration flaky on Cavium Sabre nodes Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760650] Re: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm
** Changed in: linux-kvm (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) -- 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/1760650 Title: test_074_config_security_default_mmap_min_addr in kernel security test failed with 4.4/4.15 kvm Status in QA Regression Testing: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: FAIL: test_074_config_security_default_mmap_min_addr (__main__.KernelSecurityTest) CONFIG_DEFAULT_MMAP_MIN_ADDR -- Traceback (most recent call last): File "./test-kernel-security.py", line 832, in test_074_config_security_default_mmap_min_addr self.assertEqual(self._get_config(config), expected) AssertionError: '4096' != '65536' Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 17:13:02 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1760650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760660] Re: Unable to start docker application with KVM kernel
@Po-Hsu, please check this again with linux-kvm 4.4.0-1020.25 (or later). That version enables additional cgroups, which may resolve the "dockerd[2991]: Error starting daemon: Devices cgroup ..." problem. ** Changed in: linux-kvm (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/1760660 Title: Unable to start docker application with KVM kernel Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Incomplete Bug description: When trying to install the docker.io package on 4.4 X-kvm kenrel, it will failed with: 17:34:16 DEBUG| Setting up docker.io (1.13.1-0ubuntu1~16.04.2) ... 17:34:16 DEBUG| addgroup: The group `docker' already exists as a system group. Exiting. 17:34:16 DEBUG| Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. 17:34:16 DEBUG| invoke-rc.d: initscript docker, action "start" failed. 17:34:16 DEBUG| ● docker.service - Docker Application Container Engine 17:34:16 DEBUG|Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) 17:34:16 DEBUG|Active: failed (Result: exit-code) since Mon 2018-04-02 17:34:15 UTC; 11ms ago 17:34:16 DEBUG| Docs: https://docs.docker.com 17:34:16 DEBUG| Process: 2991 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) 17:34:16 DEBUG| Main PID: 2991 (code=exited, status=1/FAILURE) 17:34:16 DEBUG| 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.542770021Z" ...t" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543167017Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543537340Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.543915385Z" ...s" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: time="2018-04-02T17:34:15.544340510Z" ...d" 17:34:16 DEBUG| Apr 02 17:34:15 harpo dockerd[2991]: Error starting daemon: Devices cgroup ...ed 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Main process exited, code...RE 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: Failed to start Docker Application Contai...e. 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Unit entered failed state. 17:34:16 DEBUG| Apr 02 17:34:15 harpo systemd[1]: docker.service: Failed with result 'exit-...'. 17:34:16 DEBUG| Hint: Some lines were ellipsized, use -l to show in full. 17:34:16 DEBUG| dpkg: error processing package docker.io (--configure): 17:34:16 DEBUG| subprocess installed post-installation script returned error exit status 1 17:34:16 DEBUG| Errors were encountered while processing: 17:34:16 DEBUG| docker.io 17:34:16 DEBUG| stderr: 17:34:16 DEBUG| W: --force-yes is deprecated, use one of the options starting with --allow instead. 17:34:16 DEBUG| E: Sub-process /usr/bin/dpkg returned an error code (1) 17:34:16 INFO | ERROR ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1522690456localtime=Apr 02 17:34:16 Command failed, rc=100, Command returned non-zero exit status If this is not supported, we can blacklist this test. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 17:34:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762237] Re: BUG: unable to handle kernel paging request at ffffd913ad935e20
Hi Joseph, I was having a similar bug; see 1759865, 1760461, 1759947 I tried getting that kernel installed. Without nvidia driver, I couldn't get the system booted. With it, I couldn't get the kernel to install. After some time, grub-install no longer worked, even from liveusb or recovery. I ended up "Erase disk and reinstall Ubuntu" last weekend and this report is from the new system. I am wondering if this problem is being caused by the 128gb of ram. I don't seem to have similar problems with the 32gb laptop running 16.04. Also, I thought the system was just unstable, but I played Uplink last night for 5 hours without any errors in dmesg. It seems to have more problems w/ browser activity (Firefox in this report, but tons more crashes since installing Chrome for work). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762237 Title: BUG: unable to handle kernel paging request at d913ad935e20 Status in linux package in Ubuntu: Incomplete Bug description: gnome-system-monitor, wget and firefox were running while I was away from the machine. Came back and the machine showed a Firefox crash popup. Before I could check what happened the machine was locked up requiring hard reboot. ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 23:48:28 2018 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: filemap_map_pages+0x96/0x390 RSP: a8d253dd7ce8 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=a8e0397c-deae-46f2-9061-c92f75295829 ro pcie_aspm=off nvme_core.default_ps_max_latency_us=0 reboot=pci vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: unable to handle kernel paging request at d913ad935e20 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd12/21/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
--- Comment From grom...@br.ibm.com 2018-04-10 14:13 EDT--- AT_BASE_PLATFORM is advertised correctly in AUXV: gromero@ltc-wspoon3:~$ uname -a Linux ltc-wspoon3 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:17:42 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux gromero@ltc-wspoon3:~$ egrep "Model|AT_PLATFORM|AT_BASE_PLATFORM" <(lscpu; LD_SHOW_AUXV=1 /bin/true) Model: 2.2 (pvr 004e 1202) Model name: POWER9 (raw), altivec supported AT_PLATFORM: power9 AT_BASE_PLATFORM:power9 TESTED. Thank you. ** Tags removed: verification-done-artful ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759312 Title: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that rely on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information. This bug is fixed by commit e4b79900222b, which is in linux-next and just landed in mainline, but is not contained in any release as of yet. == Fix == e4b79900222b ("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ---Problem Description--- AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 ---Additional Hardware Info--- Architecture:ppc64le Byte Order: Little Endian CPU(s): 176 On-line CPU(s) list: 0-175 Thread(s) per core: 4 Core(s) per socket: 22 Socket(s): 2 NUMA node(s):8 Model: 2.2 (pvr 004e 1202) Model name: POWER9, altivec supported CPU max MHz: 2800. CPU min MHz: 2300. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-87 NUMA node8 CPU(s): 88-175 NUMA node250 CPU(s): NUMA node251 CPU(s): NUMA node252 CPU(s): NUMA node253 CPU(s): NUMA node254 CPU(s): NUMA node255 CPU(s): Machine Type = P9, DD2.2, Witherspoon, baremetal ---Steps to Reproduce--- AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that relie on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information show a error message like: gromero@ltc-wspoon3:/boot$ operf NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM AT_PLATFORM: power9; AT_BASE_PLATFORM: (null) Unable to obtain cpu_type Verify that a pre-1.0 version of OProfile is not in use. If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile installation, and use its 'opcontrol' command, passing the --deinit option. Unable to ascertain cpu type. Exiting. ---uname output--- linux-image-4.13.0-36-generic 4.13.0-36.40 Userspace tool common name: operf, opreport Dear maintainer. please consider applying the following fix that's already available upstream: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
sorry, mirror status clobbered the tag back to 'verification-needed- artful'. I've set it to 'verification-done-artful' once again. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759312 Title: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that rely on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information. This bug is fixed by commit e4b79900222b, which is in linux-next and just landed in mainline, but is not contained in any release as of yet. == Fix == e4b79900222b ("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ---Problem Description--- AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 ---Additional Hardware Info--- Architecture:ppc64le Byte Order: Little Endian CPU(s): 176 On-line CPU(s) list: 0-175 Thread(s) per core: 4 Core(s) per socket: 22 Socket(s): 2 NUMA node(s):8 Model: 2.2 (pvr 004e 1202) Model name: POWER9, altivec supported CPU max MHz: 2800. CPU min MHz: 2300. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-87 NUMA node8 CPU(s): 88-175 NUMA node250 CPU(s): NUMA node251 CPU(s): NUMA node252 CPU(s): NUMA node253 CPU(s): NUMA node254 CPU(s): NUMA node255 CPU(s): Machine Type = P9, DD2.2, Witherspoon, baremetal ---Steps to Reproduce--- AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that relie on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information show a error message like: gromero@ltc-wspoon3:/boot$ operf NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM AT_PLATFORM: power9; AT_BASE_PLATFORM: (null) Unable to obtain cpu_type Verify that a pre-1.0 version of OProfile is not in use. If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile installation, and use its 'opcontrol' command, passing the --deinit option. Unable to ascertain cpu type. Exiting. ---uname output--- linux-image-4.13.0-36-generic 4.13.0-36.40 Userspace tool common name: operf, opreport Dear maintainer. please consider applying the following fix that's already available upstream: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759312] Re: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
Hi. It's fixed on 4.13.0-39-generic #44-Ubuntu build. Thanks. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759312 Title: AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that rely on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information. This bug is fixed by commit e4b79900222b, which is in linux-next and just landed in mainline, but is not contained in any release as of yet. == Fix == e4b79900222b ("powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ---Problem Description--- AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 ---Additional Hardware Info--- Architecture:ppc64le Byte Order: Little Endian CPU(s): 176 On-line CPU(s) list: 0-175 Thread(s) per core: 4 Core(s) per socket: 22 Socket(s): 2 NUMA node(s):8 Model: 2.2 (pvr 004e 1202) Model name: POWER9, altivec supported CPU max MHz: 2800. CPU min MHz: 2300. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-87 NUMA node8 CPU(s): 88-175 NUMA node250 CPU(s): NUMA node251 CPU(s): NUMA node252 CPU(s): NUMA node253 CPU(s): NUMA node254 CPU(s): NUMA node255 CPU(s): Machine Type = P9, DD2.2, Witherspoon, baremetal ---Steps to Reproduce--- AT_BASE_PLATFORM in AIXV is not exported to userspace on P9 baremetal machines causing trouble to userspace tools and software that relie on that information, notably operf and opreport (from oprofile 1.2.0+) will refuse to run without that information show a error message like: gromero@ltc-wspoon3:/boot$ operf NULL returned for one or both of AT_PLATFORM/AT_BASE_PLATFORM AT_PLATFORM: power9; AT_BASE_PLATFORM: (null) Unable to obtain cpu_type Verify that a pre-1.0 version of OProfile is not in use. If the /dev/oprofile/cpu_type file exists, locate the pre-1.0 OProfile installation, and use its 'opcontrol' command, passing the --deinit option. Unable to ascertain cpu type. Exiting. ---uname output--- linux-image-4.13.0-36-generic 4.13.0-36.40 Userspace tool common name: operf, opreport Dear maintainer. please consider applying the following fix that's already available upstream: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=e4b79900222b8cccd4da4a7a89581f Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762468] Re: Cryptoswap not working in Bionic
Yes, the problem does occur in mainline 4.16 and I have added the requested tag. If anything, 4.16.1 seems slower than 4.15 release kernel even for no cryptswap. It could be that my disk is too slow for cryptswap, but it did work in 17.10. The obvious work around is not to use cryptswap, of course. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762468 Title: Cryptoswap not working in Bionic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I have cryptoswap set up both with the 2 GB default swap file and an 8 GB swap partition with 8 GB of ram. However, the system does not use this swap when it should. For example, if I run a little test code which attempts to allocate 10 GB of memory in 1 GB chuncks, the system hangs with no obvious use of swap. E.g. running top shows no swap use before the hang. However, if I replace cryptoswap by standard swap, it works as expected: allocates the requested memory and exits, using swap. Of course, my disk is slow, so this takes some time but it does work. I originally noticed this problem when compiling a very large application. The system would hang on ld. I've checked hardware using memtest and stress. No problems. This took me days to track down but I'm 99% certain now that the problem is with cryptoswap. If I compile with cryptoswap: hang. If I compile with standard swap: no problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: weinberg 2425 F pulseaudio /dev/snd/controlC0: weinberg 2425 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 11:57:23 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 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:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762652] Re: perf DWARF unwind failed
Well this is more about the user space tool perf, not really the kernel itself. And I can't really imagine why DWARF unwinding would have anything to do with the kernel used. I'm on stock ubuntu 4.13.0-38-generic btw. When I compile perf from the kernel source (commit 2bf1ab321a06a7faeb95c56d02139140fb56199a) it seems that it fails when only having libdw-dwarf-unwind as system feature. When having both libdw-dwarf-unwind and libunwind available the compiled perf does not fail the test. I think that for DWARF unwinding either one of those two libraries should be enough, so maybe this is a bug in libdwarf or how perf uses libdwarf, and when libunwind is available it uses it instead. But just a wild guess, I don't really know what's going on. In any case, a quick "fix" seems to be building perf with libunwind - even if that just masks the actual bug here. ** 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/1762652 Title: perf DWARF unwind failed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10. To reproduce: $ perf test [...] 57: DWARF unwind : FAILED! [...] It seems perf is somehow mis-configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762757] Re: RDMA/hns: ensure for-loop actually iterates and free's buffers
** Changed in: linux (Ubuntu) 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/1762757 Title: RDMA/hns: ensure for-loop actually iterates and free's buffers Status in linux package in Ubuntu: Fix Committed Bug description: We backported RDMA/hns support for HiSilicon hip08 systems in bug 1756097. I noticed that there's a new commit that fixes a bug in this support that should also be backported: commit 38759d6175d338fbf9282c8ea2b51f3b7ab9bc98 Author: Colin Ian King Date: Mon Mar 26 16:10:18 2018 +0100 RDMA/hns: ensure for-loop actually iterates and free's buffers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I started a kernel bisect between v4.15-rc2 and v4.15-rc3. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 78d9b048446c3c0a83313444fb706f8f3bccdae7 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1761751 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762755] Re: Support cq/rq record doorbell for RDMA on HSilicon hip08 systems
** Changed in: linux (Ubuntu) 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/1762755 Title: Support cq/rq record doorbell for RDMA on HSilicon hip08 systems Status in linux package in Ubuntu: Fix Committed Bug description: HiSilicon hip08 systems support a cq/rq record feature for RDMA that is currently not supported by the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp