[Kernel-packages] [Bug 1814728] Re: linux-raspi2: 4.15.0-1032.34 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/ovFRgi6V/764-pi- kernel-4150-103234-23-18-pi3 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1814728 Title: linux-raspi2: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: 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: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 15:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814728] Re: linux-raspi2: 4.15.0-1032.34 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Description changed: 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: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 15:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: Pending -- snap not in 18-pi3/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1814728 Title: linux-raspi2: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: 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: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 15:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in 18-pi3/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio
Autopkgtests on cosmic started passing (as far as this bug is concerned − there were other unrelated failures) on 2018-10-10, when openjdk-lts was upgraded from 10.0.2+13-1ubuntu1 to 11~28-3ubuntu1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805429] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-02-19 03:45 EDT--- This information is already available with kernel 4.20, therefore can be made public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805429 Title: [19.04 FEAT] Extended access controls for AP queue - kernel part Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Update description: Provide a means to control which user/process can access which APQN, or in other words enable to grant users/applications access to different (sets of) crypto adapters and domains. While keeping existing interfaces for compatibility, allow to use both DAC (e.g. Unix file permissions) and MAC (e.g. LSM) methods. Please enable the following kernel config option: * CONFIG_ZCRYPT_MULTIDEVNODES=y will be made available with kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814726] Re: linux: 4.15.0-46.49 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: 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 -- backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 1814743 (linux-azure), bug 1814744 (linux-gcp), bug 1814745 (linux-hwe), bug 1814746 (linux-hwe-edge), bug 1814747 (linux-oracle) boot-testing-requested: true bugs-spammed: true derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 (linux-aws), bug 1814733 (linux-azure), bug 1814734 (linux-gcp), bug 1814736 (linux-kvm), bug 1814738 (linux-oracle) phase: Testing phase-changed: Sunday, 17. February 2019 17:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in 18/candidate channel verification-testing: Ongoing -- testing 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/1814726 Title: linux: 4.15.0-46.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- backports: bug 1814741 (linux-azure), bug 1814742 (linux-aws-hwe), bug 1814743 (linux-azure), bug 1814744 (linux-gcp), bug 1814745 (linux-hwe), bug 1814746 (linux-hwe-edge), bug 1814747 (linux-oracle) boot-testing-requested: true bugs-spammed: true derivatives: bug 1814728 (linux-raspi2), bug 1814730 (linux-oem), bug 1814731 (linux-aws), bug 1814733 (linux-azure), bug 1814734 (linux-gcp), bug 1814736 (linux-kvm), bug 1814738 (linux-oracle) phase: Testing phase-changed: Sunday, 17. February 2019 17:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in 18/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
3.13.0-166.216 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883) ubuntu_kvm_unit_tests - 16 failed on gonzo, 9 failed on KVM nodes ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 (bug 1774394) fanotify06 (bug 1775378) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_kvm_smoke_test - getlogin will fail to open /proc/self/loginuid (bug 1770245) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fcntl35 / fcntl35_64 (bug 1774394) fanotify06 (bug 1775378) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - test_130_config_debug_rodata (bug 1747850) test 021, 022 (bug 1747847) test 050 (bug 1684776) Issue to note in i386: ubuntu_kvm_smoke_test - Unable to start KVM, timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 (bug 1774394) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 (bug 1775153) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) openat03 (bug 1798027) request_key03 (bug 1798052) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 failed with T/X/A/B kernel (bug 1775153) fanotify11 timeouted (bug 1808107) keyctl02 (bug 1798022) keyctl06 (bug 1798025) open14 (bug 1798061) openat03 (bug 1798027) request_key03 (bug 1798052) ubuntu_lxc - failed to fetch GPG key ubuntu_qrt_kernel_security - test_ulimit_stack_small failed on PPC64 (bug 1816467) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 11. February 2019 20:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Description changed:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
- [...]
+ ...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816467] Re: test_ulimit_stack_small in ubuntu_qrt_kernel_security failed on PPC64
*** This bug is a duplicate of bug 1814295 *** https://bugs.launchpad.net/bugs/1814295 ** This bug has been marked a duplicate of bug 1814295 qa-regression-testing test_ulimit_stack_small fails on ppc64el -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816467 Title: test_ulimit_stack_small in ubuntu_qrt_kernel_security failed on PPC64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This test is expecting to throw a return code 137 or 139, but it got 0 instead ulimit -s 1 && /bin/true echo $? After that, if you try to run top command, it will failed with segfault. FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2855, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139, 137 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1816467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker
** Description changed: 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: 1814749 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:06 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814759 Title: linux-gcp: 4.18.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: 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: 1814749 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:06 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805429] Re: [19.04 FEAT] Extended access controls for AP queue - kernel part
We already have this option turned on in our 5.0 tree. I've marked this as an enforced option in our annotations to ensure it is not accidentally turned off and added a note referring to this bug. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1805429 Title: [19.04 FEAT] Extended access controls for AP queue - kernel part Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Fix Committed Bug description: Update description: Provide a means to control which user/process can access which APQN, or in other words enable to grant users/applications access to different (sets of) crypto adapters and domains. While keeping existing interfaces for compatibility, allow to use both DAC (e.g. Unix file permissions) and MAC (e.g. LSM) methods. Please enable the following kernel config option: * CONFIG_ZCRYPT_MULTIDEVNODES=y will be made available with kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800566] Re: Make the reset_devices parameter default for kdump kernels
Debdiffs for this bug were attached to LP#1800562 ** Description changed: [Impact] Crash kernels do not advise some subsystems to perform a reset by default. [Description] Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test - [...] + ... kexec command to be used: - /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz + /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline. The fix will be tested with autopkgtests and normal kdump use-case scenarios. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800566 Title: Make the reset_devices parameter default for kdump kernels Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Cosmic: Confirmed Status in makedumpfile source package in Disco: Confirmed Bug description: [Impact] Crash kernels do not advise some subsystems to perform a reset by default. [Description] Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus. This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. [Test Case] 1) Deploy a Disco VM e.g. with uvt-kvm 2) Install the kdump-tools package 3) Run `kdump-config test`and check for the 'reset_devices' parameter: $ kdump-config test ... kexec command to be used: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz [Regression Potential] The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline. The fix will be tested with autopkgtests and normal kdump use-case scenarios. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813733] Re: Ignore "incomplete report" from Elan touchpanels
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813733 Title: Ignore "incomplete report" from Elan touchpanels Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] When using Elan touchpanels, this message keeps getting spurted out: [ 136.138487] i2c_hid i2c-DELL08D6:00: i2c_hid_get_input: incomplete report (14/65535) This is an error message, so systemd-journald flushes to disk as soon as the message shows. This prevents the storage enters power saving state, hurting battery time. Other than the annoying message, the touchpad itself works fine. [Fix] Just warn once to avoid the annoying message. [Test] The annoying message stops once the fix applied. [Regression Potential] None. The user still gets the warning from dmesg without all the flooding. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1813733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812812] Re: Fix non-working QCA Rome Bluetooth after S3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812812 Title: Fix non-working QCA Rome Bluetooth after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] Sometimes QCA Rome Bluetooth USB host doesn't work after S3: [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110) This is due to USB core enables LPM two times after S3. [Fix] Only enable LPM once. [Test] The Bluetooth USB works all the time after applying the fix. [Regression Potential] Low. Enabling a hardware feature twice in a row isn't right, I'd be surprise if any hardware relies on this driver behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1812812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: 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: 1814749 - phase: Promote to Proposed - phase-changed: Tuesday, 19. February 2019 07:06 UTC + phase: Testing + phase-changed: Tuesday, 19. February 2019 09:37 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814759 Title: linux-gcp: 4.18.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: 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: 1814749 phase: Testing phase-changed: Tuesday, 19. February 2019 09:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
Hi your working on this stuff is excellent. Even everyone is sharing here nice ideas with lot of new stuff. Further you can try something more regarding to your requirement at https://activators4windows.com/2018/10/14/windows-7-loader-activator/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443924]
Hi your working on this stuff is excellent. Even everyone is sharing here nice ideas with lot of new stuff. Further you can try something more regarding to your requirement at https://activators4windows.com/2018/10/14/windows-7-loader-activator/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Won't Fix Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio
As evidenced by http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/i386, the problem went away in cosmic at some point in November 2018. xenial and bionic are still affected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805429] Re: [19.04 FEAT] Extended access controls for AP queue - kernel part
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805429 Title: [19.04 FEAT] Extended access controls for AP queue - kernel part Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Update description: Provide a means to control which user/process can access which APQN, or in other words enable to grant users/applications access to different (sets of) crypto adapters and domains. While keeping existing interfaces for compatibility, allow to use both DAC (e.g. Unix file permissions) and MAC (e.g. LSM) methods. Please enable the following kernel config option: * CONFIG_ZCRYPT_MULTIDEVNODES=y will be made available with kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker
** Description changed: 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: 1814726 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:33 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814730 Title: linux-oem: 4.15.0-1034.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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: 1814726 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:33 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker
** Description changed: 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: 1814749 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:06 UTC reason: - promote-to-proposed: Ongoing -- packages copies requested + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814759 Title: linux-gcp: 4.18.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: 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: 1814749 phase: Promote to Proposed phase-changed: Tuesday, 19. February 2019 07:06 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
Has this been tested with Disco (19.04) or Cosmic (18.10)? IOW does this issue with ndctl only exist in Bionic, or does it carry forward? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: 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: 1814726 - phase: Promote to Proposed - phase-changed: Tuesday, 19. February 2019 07:33 UTC + phase: Testing + phase-changed: Tuesday, 19. February 2019 10:08 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814730 Title: linux-oem: 4.15.0-1034.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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: 1814726 phase: Testing phase-changed: Tuesday, 19. February 2019 10:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805429] Re: [19.04 FEAT] Extended access controls for AP queue - kernel part
** Changed in: ubuntu-z-systems Status: Incomplete => 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/1805429 Title: [19.04 FEAT] Extended access controls for AP queue - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Update description: Provide a means to control which user/process can access which APQN, or in other words enable to grant users/applications access to different (sets of) crypto adapters and domains. While keeping existing interfaces for compatibility, allow to use both DAC (e.g. Unix file permissions) and MAC (e.g. LSM) methods. Please enable the following kernel config option: * CONFIG_ZCRYPT_MULTIDEVNODES=y will be made available with kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 11. February 2019 20:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 11. February 2019 20:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811394] Re: ipset kernel error: 4.15.0-43-generic
I will try to do that. I've narrowed down the versions for now (using mainline kernel). The bug appeared sometime between 4.13.16 and 4.14.0 and was fixed between 4.15.18 and 4.16.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811394 Title: ipset kernel error: 4.15.0-43-generic Status in linux package in Ubuntu: Confirmed Bug description: When running the following script: https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear on the 4.15.0-43-generic kernel it leads to a kernel panic. Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no problems with those. The issue was first mentioned in our forum (https://forum.proxmox.com/threads/kernel-panic- ip_set_hash_net.50138/#post-234532) on our own kernel that's based on the Ubuntu 4.15. After further investigations neither Debian 9 (4.9 kernel) nor Arch Linux (4.20 kernel) exhibited that same issue. The attached log has the errors of one run of the ipset-nuclear script. The kernel panic on the host side can also be triggered from an unprivileged container (Arch Linux, LXC) --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 31 12:29 seq crw-rw+ 1 root audio 116, 33 Jan 31 12:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3f9884ba-1593-11e9-a795-9abe83d987a0 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814744] Re: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: 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: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 17:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814744 Title: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 17:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: 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: 1814749 phase: Testing phase-changed: Tuesday, 19. February 2019 09:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1814759 Title: linux-gcp: 4.18.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: 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: 1814749 phase: Testing phase-changed: Tuesday, 19. February 2019 09:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend
Affects also laptop HP Spectre x360 - 15-df0008nc with nvidia-driver-415. The only workaround which seems to work is to use kernel parameters acpi_osi=! acpi_osi=\"Windows 2009\", but that disables the touchpad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809247] Re: package linux-headers-4.15.0-43 4.15.0-43.46 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation n
I'm getting this too. It is after a crash in the popup notification. I click "send" on the dialog asking to send an error report, then I get the window saying "saving crash reporting state failed" Ubuntu MATE 18.10 ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809247/+attachment/5239879/+files/Selection_618.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809247 Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- headers-4.15.0-43.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: The following copied from screenshot 2018-12-20 11-50-53 Saving crash reporting state failed, Can't set auto auto or never reporting mode. Command '['/usr/bin/gdbus','call','-y','-d', 'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/ WhoopsiePreferences','-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-43 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Thu Dec 20 11:22:53 2018 Dependencies: DuplicateSignature: package:linux-headers-4.15.0-43:4.15.0-43.46 Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ... dpkg: error processing archive /tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb (--unpack): unable to open '/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted InstallationDate: Installed on 2017-12-03 (382 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: linux Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239902/+files/XorgLogOld.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239895/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239900/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239901/+files/XorgLog.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239904/+files/xdpyinfo.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239899/+files/UnitySupportTest.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796839] Re: Only 64 Memory regions or dimms supported for Hotplug.
Thanks. Closing bug out. ** Changed in: ubuntu-power-systems Status: Incomplete => Won't Fix ** 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/1796839 Title: Only 64 Memory regions or dimms supported for Hotplug. Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1796839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816251] Re: [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep mode and sometimes is shutdown by BIOS overheating protection
*** This bug is a duplicate of bug 1803179 *** https://bugs.launchpad.net/bugs/1803179 It seems to be related to nvidia drivers. The previous behavior was described for nvidia-driver-390. After upgrading to nvidia-driver-415 it is observed the same behavior as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179. (the laptop freeze in sleep mode) The only workaround which works is to use kernel parameters acpi_osi=! acpi_osi=\"Windows 2009\", but that disables the touchpad. ** This bug has been marked a duplicate of bug 1803179 System does not reliably come out of suspend -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816251 Title: [HP Spectre x360 - 15-df0008nc] Battery is drained in the laptop sleep mode and sometimes is shutdown by BIOS overheating protection Status in linux package in Ubuntu: Confirmed Bug description: [HP Spectre x360 - 15-df0008nc] Battery is significantly drained in the laptop sleep mode. Over the night the fully charged laptop battery will get empty while kept the laptop in sleep mode. The symptoms are the same with or without connected USB-C dock. As a workaround also it is not possible to enable deep sleep. Full laptop specification is here: https://support.hp.com/za-en/document/c06200426 Enabling deep sleep results into failure: $ sudo echo deep > /sys/power/mem_sleep bash: /sys/power/mem_sleep: Permission denied. Additionally also not possible to enable deep sleep by updating grub loader. # editing /etc/default/grub # Adding GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" sudo update-grub # reboot laptop and still gets s2idle $ cat /sys/power/mem_sleep [s2idle] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-power-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 18:22:25 2019 InstallationDate: Installed on 2019-02-13 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2055 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-13 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Spectre x360 Convertible 15-df0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=00f2f7ce-f972-4459-afbe-9f134e1dcae2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/13/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.45 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd12/13/2018:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.45:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2039 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-13 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Spectre x360 Convertible 15-df0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=00f2f7ce-f972-4459-afbe-9f134e1dcae2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A
[Kernel-packages] [Bug 1816564] 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/1816564 Title: java breaks on this kernel Status in linux package in Ubuntu: Confirmed Bug description: I reverted back to 4.15.0-20-generic for proper java operations gge@jasperserver:~$ java -version java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) with kernel 4.15.0-45-generic java processes just get terminated: root@jasperserver:/opt# java -jar jboss-eap-6.4.0-installer.jar Exception in thread "Thread-1" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) Select language : 0: eng 1: chn 2: deu 3: fra 4: jpn 5: por 6: spa Please choose [0] : Invalid file. Please specify the correct XML file. root@jasperserver:/opt# root@jasperserver:/opt/EAP-6.4/bin# ./jboss-cli.sh Exception in thread "Thread-2" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] root@jasperserver:/opt/EAP-6.4/bin# ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 19 13:34:12 2019 HibernationDevice: RESUME=/dev/mapper/jasperserver--vg-swap_1 InstallationDate: Installed on 2019-02-15 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809934] Re: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot
I think I am suffering from a related bug. Asrock X370 Taichi, BIOS 5.10 (2018-12-21). Ryzen 5 2600X. Radeon RX 580. Ubuntu 18.04.02 (HWE). I tested with kernel 4.15 and 4.18, no difference. Can not boot via GRUB with amdgpu driver, unless "amdgpu.dpm=0" is set. I only integrated the RX 580 into the build recently, after updating to BIOS 5.10 (AGESA 1.0.0.6), so I haven't yet tested previous BIOS versions with this card. I wonder if this latest BIOS update is affecting AMDGPU's DPM? https://www.asrock.com/mb/AMD/X370%20Taichi/#BIOS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809934 Title: AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot Status in linux package in Ubuntu: Incomplete Bug description: CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G Version: Ubuntu 18.04.1 Desktop (AMD64) Kernel: 4.15.0-43 generic Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c) Detailed information: AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately. However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel. If install kernel version 4.18.0-13-generic from "linux-image-generic- hwe-18.04-edge" has no issue. Here is boot messages output (dumped via serial port and truncated): [4.385021] [drm] ring test on 5 succeeded in 3 usecs [4.385030] [drm] ring test on 6 succeeded in 2 usecs [4.385035] [drm] ring test on 7 succeeded in 1 usecs [4.385044] [drm] ring test on 8 succeeded in 2 usecs [4.385090] [drm] ring test on 10 succeeded in 2 usecs [5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: [5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: [5.406006] tsc: Marking TSC unstable due to clocksource watchdog [5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214) [7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected! [ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133 [ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60] [ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779756 Title: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814539] Re: acpi is getting stuck at charging/discharging
$ git log Ubuntu-4.18.0-12.13..Ubuntu-4.18.0-13.14 --pretty=oneline bfe015d2df84299c03b3189e6a6f5d97a68b213c (tag: cod/changeset/cosmic/hash--bfe015d2df84299c03b3189e6a6f5d97a68b213c, tag: Ubuntu-4.18.0-13.14) UBUNTU: Ubuntu-4.18.0-13.14 b834bd41a001f0aa21aa877b63c245539d064b63 UBUNTU: link-to-tracker: update tracking bug dd03636af187923c3cf63fa471a02c07ad93ef7a UBUNTU: [Packaging] buildinfo -- add buildinfo support to getabis 6efd1e8d2894b530095bdf75c64107b3ed279d6f UBUNTU: [Packaging] buildinfo -- add compiler information to the flavour ABI 2d7f191a3315096bbce261fbd4a1562c440a734a UBUNTU: [Packaging] buildinfo -- add firmware information to the flavour ABI 8c9154e701ec5fb0da7cd0e495836bc06e4c873c UBUNTU: [Packaging] buildinfo -- add basic build information d70801b56935ecfb472ab4be61b9ee06326c5667 UBUNTU: [Packaging] ABI -- accumulate abi information at the end of the build bb224d4911f2a527a665be13cc9a1e31e13f46c0 UBUNTU: [Packaging] commonise debhelper invocation 6af14034d456af0c9a09de0bd2401453240efe3a UBUNTU: [Packaging] limit preparation to linux-libc-dev in headers 811bdb9c90e7058b5f58bf269c3727287ec3923e UBUNTU: [Packaging] own /usr/lib/linux/triggers 1adbe114f170a131658147f013e4f2c048a69015 Revert "net-next/hinic: add checksum offload and TSO support" c2f0cb7a8222f28eb6ffe876f406c1e3e7e161d2 cdrom: fix improper type cast, which can leat to information leak. b9565132d7340de78dbd8eec542910f6194b6fc9 UBUNTU: Start new release No ACPI changes during these two versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814539 Title: acpi is getting stuck at charging/discharging Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: As I write this I run 4.18.0-12-generic and the ACPI subsystem correctly detects when the powerplug is plugged and unplugged. In 4.18.0-13 and -14 this does not seem to be the case. The subsystem status will remain as it was when booting if the plug is removed/replaced. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.14.15 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niclangf 12325 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 4 14:47:02 2019 EcryptfsInUse: Yes HibernationDevice: InstallationDate: Installed on 2017-07-18 (566 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HGS1C200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=2d9f5e19-7a20-4479-9c37-fcc005765c98 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-02 (94 days ago) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HGS1C200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS1C200:pvrThinkPadT470s:rvnLENOVO:rn20HGS1C200:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HGS1C200 dmi.product.sku: LENOVO_MT_20HG_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1814539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814415] Re: laptop turns off when unplugged also battery percentage estimates
Please attach the output of: $ grep . /sys/class/power_supply/BAT0/* -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814415 Title: laptop turns off when unplugged also battery percentage estimates Status in linux package in Ubuntu: Confirmed Bug description: laptop turns off when unplugged also battery percentage estimates ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 2646 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 05:24:55 2019 InstallationDate: Installed on 2019-01-25 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a060 Quanta Computer, Inc. Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=bb685fe5-38ec-4d06-b916-2ef404f1e099 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA515-51G:pvrV1.10:rvnKBL:rnCharmander_KL:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19
apport information ** Tags added: apport-collected ubuntu ** Description changed: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan + --- + ProblemType: Bug + .tmp.unity_support_test.0: + + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ben7239 F pulseaudio + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading + DistroCodename: bionic + DistroRelease: Ubuntu 18.04 + DistroVariant: ubuntu + DkmsStatus: + tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built + tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed + tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed + EcryptfsInUse: Yes + GraphicsCard: + Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) +Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0a2b Intel Corp. + Bus 001 Device 003: ID 5986:055c Acer, Inc + Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Notebook W65_W67RZ + Package: xserver-xorg-input-libinput 0.27.1-1 + PackageArchitecture: amd64 + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.173.3 + Tags: bionic ubuntu ubuntu + Uname: Linux 4.15.0-45-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/27/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.05.09 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: W65_W67RZ + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: W65_W67RZ + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook + version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 + version.libdrm2: libdrm2 2.4.95-1~18.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 + version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 + version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 + xserver.bootTime: Sun Jan 21 20:00:45 2018 + xserver.configfile: default + xserver.errors: + open /dev/dri/card0: No such file or directory + open /dev/dri/card0: No such file or directory + Screen 0 deleted because of no matching config section. + AIGLX: reverting to software rendering + xserver.logfile: /var/log/Xorg.0.log + xserver.outputs: + + xserver.version: 2:1.19.5-0ubuntu2 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239882/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again.
[Kernel-packages] [Bug 1815957] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239883/+files/BootLog.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816554] Re: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816554 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: I was doin standard kernel update from vmlinuz-4.4.0-142-generic to actual. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Tue Feb 19 08:20:28 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:/var/lib/dkms/nvidia-384/384.130/build/nvidia/os-mlock.c:119:5: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2015-03-13 (1438 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.20 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 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/nvidia-graphics-drivers-384/+bug/1816554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Hi Tim, Would it be possible for you to test mainline kernel [1]? It probably requires more commits to be backported. But first let's make sure it's fully fixed in mainline kernel. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are identical, then only one drive can be seen. NQN is supposed to be unique but some Intel drives do not follow that. [Fix] The device-supplied subnqn is ignored and one will be generated as if the field is empty. The upstream patch conflicts with a value in 'enum nvme_quirks' that we added in a SAUCE patch, changed that from (1<<8) to (1<<15). [Test] With this fix, both drives can be seen. [Regression Potential] The fix limits to Intel 760p/Pro 7600p SSD, and the fix has been verified by the bug reporter. - I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
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/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
New
Status in linux-aws package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-aws source package in Cosmic:
Confirmed
Status in linux-azure source package in Cosmic:
Confirmed
Status in linux-kvm source package in Cosmic:
Confirmed
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6
ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17
Uname: Linux 4.18.0-1006-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Mon Jan 21 08:12:54 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812624/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239892/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239896/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239894/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239893/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239897/+files/RfKill.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239906/+files/xserver.devices.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] xinput.txt
apport information ** Attachment added: "xinput.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239905/+files/xinput.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239898/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Just for curiosity, how did you test if it works or not? I personally use this web program https://webcammictest.com/check- microphone.html So I can hear myself, and for me it is still present with every workaround I try... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
The attachment "debdiff for disco" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816564] [NEW] java breaks on this kernel
Public bug reported: I reverted back to 4.15.0-20-generic for proper java operations gge@jasperserver:~$ java -version java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) with kernel 4.15.0-45-generic java processes just get terminated: root@jasperserver:/opt# java -jar jboss-eap-6.4.0-installer.jar Exception in thread "Thread-1" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) Select language : 0: eng 1: chn 2: deu 3: fra 4: jpn 5: por 6: spa Please choose [0] : Invalid file. Please specify the correct XML file. root@jasperserver:/opt# root@jasperserver:/opt/EAP-6.4/bin# ./jboss-cli.sh Exception in thread "Thread-2" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] root@jasperserver:/opt/EAP-6.4/bin# ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 19 13:34:12 2019 HibernationDevice: RESUME=/dev/mapper/jasperserver--vg-swap_1 InstallationDate: Installed on 2019-02-15 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1816564 Title: java breaks on this kernel Status in linux package in Ubuntu: New Bug description: I reverted back to 4.15.0-20-generic for proper java operations gge@jasperserver:~$ java -version java version "1.8.0_191" Java(TM) SE Runtime Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) with kernel 4.15.0-45-generic java processes just get terminated: root@jasperserver:/opt# java -jar jboss-eap-6.4.0-installer.jar Exception in thread "Thread-1" java.lang.RuntimeException: broken pipe at org.jboss.aesh.console.reader.ConsoleInputSession$2.run(ConsoleInputSession.java:95) Select language : 0: eng 1: chn 2: deu 3: fra 4: jpn 5: por 6: spa Please choose [0] : Invalid file. Please specify the correct XML file. root@jasperserver:/opt# root@jasperserver:/opt/EAP-6.4/bin# ./jboss-cli.sh Exception in thread "Thread-2" java.lang.RuntimeException: broken pipe at
[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
John, please try usb-storage quirks as described here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/kernel-parameters.txt#n4812 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Changed in: makedumpfile (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
In Progress
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239891/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239903/+files/Xrandr.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239890/+files/MonitorsUser.xml.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816554] [NEW] nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build
Public bug reported: I was doin standard kernel update from vmlinuz-4.4.0-142-generic to actual. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Tue Feb 19 08:20:28 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:/var/lib/dkms/nvidia-384/384.130/build/nvidia/os-mlock.c:119:5: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2015-03-13 (1438 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.20 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816554 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: I was doin standard kernel update from vmlinuz-4.4.0-142-generic to actual. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-384 384.130-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Tue Feb 19 08:20:28 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:/var/lib/dkms/nvidia-384/384.130/build/nvidia/os-mlock.c:119:5: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2015-03-13 (1438 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 384.130-0ubuntu0.14.04.1 RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.20 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 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/nvidia-graphics-drivers-384/+bug/1816554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803179] Re: System does not reliably come out of suspend
Additionally it seems for HP Spectre x360 - 15 (with nvidia-driver-415) that also the battery is drained and the laptop is getting warm in the sleep mode. By switching to Intel card (PRIME profile Intel) the sleep mode seems to work well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816493] Re: Ralink RT3290 Is Not in Kernel
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.0-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816493 Title: Ralink RT3290 Is Not in Kernel Status in linux package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Bluetooth in HP laptop doesn't work, because the driver isn't in the kernel or packaged. There are some guides in the internet, but they aren't integrated in kernel and aren't guaranteed to work. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 19 01:33:46 2019 InstallationDate: Installed on 2019-02-07 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no syslog: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherif 5874 F pulseaudio CRDA: global country EG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-02-07 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=62a6c247-4374-447e-9f08-9ff03782230d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: cosmic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1814539] Re: acpi is getting stuck at charging/discharging
Please do a kernel bisection between v4.18 to v5.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814539 Title: acpi is getting stuck at charging/discharging Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: As I write this I run 4.18.0-12-generic and the ACPI subsystem correctly detects when the powerplug is plugged and unplugged. In 4.18.0-13 and -14 this does not seem to be the case. The subsystem status will remain as it was when booting if the plug is removed/replaced. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-generic 4.18.0.14.15 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niclangf 12325 F pulseaudio CurrentDesktop: KDE Date: Mon Feb 4 14:47:02 2019 EcryptfsInUse: Yes HibernationDevice: InstallationDate: Installed on 2017-07-18 (566 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HGS1C200 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=2d9f5e19-7a20-4479-9c37-fcc005765c98 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-11-02 (94 days ago) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HGS1C200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS1C200:pvrThinkPadT470s:rvnLENOVO:rn20HGS1C200:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HGS1C200 dmi.product.sku: LENOVO_MT_20HG_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1814539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239884/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239887/+files/DpkgLog.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239885/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239886/+files/Dependencies.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239889/+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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815957] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1815957/+attachment/5239888/+files/IwConfig.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/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben7239 F pulseaudio CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 5986:055c Acer, Inc Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook W65_W67RZ Package: xserver-xorg-input-libinput 0.27.1-1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic ubuntu ubuntu Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.09 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_W67RZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W65_W67RZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jan 21 20:00:45 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
Sorry for the late reply. Sent a patch: https://lkml.org/lkml/2019/2/19/513 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810797] Re: bluetooth controller not detected with 4.15 kernel
This passes for me on 4.15.0-46.49 - (rev 82) kernel snap that is
currently in candidate
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810797
Title:
bluetooth controller not detected with 4.15 kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-snapdragon source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Fix Committed
Status in linux-snapdragon source package in Cosmic:
Invalid
Bug description:
Impact:
Upon boot, no hci device is available to userspace, thus bluetooth
communication is not possible.
Defect analysis:
The root of the problem lies in these two patches:
$ git log --online drivers/bluetooth/btqcomsmd.c
...
766154b Bluetooth: btqcomsmd: retrieve BD address from DT property
6e51811 Bluetooth: btqcomsmd: Add support for BD address setup
...
Qualcomm engineer found that btqcomsmd had no BD address burned in
(nor via ROM, neither internally) and it was always coming up with the
same address, probably derived from manufacturer ID and / or chip ID.
To fix this, they pushed the burden of generating a unique per-board
BD address to the Qualcomm bootloader and make it pass down via DTB to
the live kernel - and if no address was present in the DTB, the hci
was left unconfigured.
Fix:
So *technically* speaking, the kernel is correct in this case, it's
our dragonboard image (e.g. Ubuntu Core) that doesn't extract the
generated BD address from the Qualcomm bootloader and pass it down to
the kernel.
On the other hand, having Bluetooth working out of the box (even with
a dummy address), is a nice feature to have, so i slightly modified
Qualcomm's code introduced in the two above patches, and made the lack
of BD address in DTB non fatal:
if BD_is_present_in_DTB()
read_BD_and_apply_setup()
else
let_hci_core_generate_BD()
end if
And surrounded the modification in #ifdef...#endif brackets to keep it
local.
How to test:
By default, on a patched kernel, the hci device will have a default
address:
ubuntu@dragon410c:~$ hcitool dev
Devices:
hci000:00:00:00:5A:AD
the address " 00:00:00:00:5A:AD" might vary, but will be consistent
after every reboot.
The other option is to specify a custom BD address, e.g. using uboot
to manipulate the dtb - we assume the dtb was loaded in memory at
${fdt_addr}:
dragonboard410c => fdt addr ${fdt_addr}
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
compatible = "qcom,wcnss-bt";
};
dragonboard410c => fdt resize
dragonboard410c => fdt set /soc/wcnss/smd-edge/wcnss/bt/ local-bd-
address [ 55 44 33 22 11 00 ]
dragonboard410c => fdt print /soc/wcnss/smd-edge/wcnss/bt/
bt {
local-bd-address = [55 44 33 22 11 00];
compatible = "qcom,wcnss-bt";
};
then proceed with the rest of the boot process and check hci:
$ hcitool dev
Devices:
hci000:11:22:33:44:55
In both cases, blueooth work afterward, and can be used to communicate
with other devices:
ubuntu@dragon410c:~$ hcitool scan
Scanning ...
C0:BD:54:12:4E:D1 My dummy device
Regression potential:
None, the fix is surronded with #ifdef...#endif thus it doesn't exist
outside of it.
--
Using the core18 image from
http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/
Kernel snap: 4.15.0-39.42 (72)
rfkill shows there is an hci0 device:
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
But bluetoothctl does not detect any controller:
$ sudo bluetoothctl
08:58 Agent registered
08:58 [bluetooth]# list
[...no output...]
If you revert to the 4.4 kernel [4.4.0-1106.111 (76)] it works:
$ sudo bluetoothctl
[NEW] Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
Agent registered
[bluetooth]# list
Controller 00:00:00:00:5A:AD BlueZ 5.47 [default]
[bluetooth]# show
Controller 00:00:00:00:5A:AD
Name: BlueZ 5.47
Alias: BlueZ 5.47
Class: 0x
Powered: no
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID:
[Kernel-packages] [Bug 1816091] Re: linux-azure: 4.15.0-1039.41~14.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816091 Title: linux-azure: 4.15.0-1039.41~14.04.2 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1816093 phase: Testing phase-changed: Monday, 18. February 2019 09:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816093] Re: linux-azure: 4.15.0-1039.43 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816093 Title: linux-azure: 4.15.0-1039.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1813779 phase: Testing phase-changed: Monday, 18. February 2019 23:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816091] Re: linux-azure: 4.15.0-1039.41~14.04.2 -proposed tracker
** Description changed: 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: 1816093 phase: Testing phase-changed: Monday, 18. February 2019 09:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-security: Holding -- stakeholder signoff not verified + promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816091 Title: linux-azure: 4.15.0-1039.41~14.04.2 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1816093 phase: Testing phase-changed: Monday, 18. February 2019 09:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- stakeholder signoff not verified promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Description changed: 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: 1816081 phase: Testing phase-changed: Monday, 18. February 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: 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: 1816081 phase: Testing phase-changed: Monday, 18. February 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: 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: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-security: Holding -- stakeholder signoff not verified + promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: 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: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- stakeholder signoff not verified promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N
This is a kernel issue and we have seen this with upstream kernels and verified the fixes on upstream kernels. I expect bionic kernel 4.15 and above kernels to display this defect. Although I have not tried applying only the kernel fix on bionic, the test kernel shared above shows that original defect is resolved, however another one has popped up. This indicates that a few more patches are required to get the complete namespace modification functionality working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811660 Title: [SRU] Unable to modify/create-namespace over NVDIMM-N Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Users are unable to modify or create namespaces over NVDIMM-N [Test Case] Steps to Reproduce: 1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & NVDIMM firmware to latest available to customers. 2. Install and boot to Ubuntu 18.04 3. Notice that no pmems are enumerated. 4. Try #ndctl create-namespace -> Failure with device or resource busy. Actual results: No pmems are enumerated, cannot create namespaces. If pmems are already present, then cannot modify the namespaces. Expected results: namespace creation should be possible [Regression Potential] The Regression Risk is low, Intel not impacted but Dell is. [Other Info] Additional Info: * Seen with upstream linux-4.20.2 also. * Upstream bug report - https://github.com/pmem/ndctl/issues/78 * Upstream kernel patch: https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html Request you to incorporate it in bionic and xenial kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel
Please forgive if this comment is outside etiquette. I am trying to install Ubuntu or Debian on a Dell Poweredge 750, and get this error after a few minutes of uptime: aacraid: Host adapter abort request (0,0,0,0) [repeat >15x] AAC: Host adapter BLINK LED 0xc7 AAC0: adapter kernel panic'd c7. [last two lines repeat again twice] Am installing in a workplace at request of IS Dept manager, to determine feasibility of using Linux on a server to run SQL server. If it fails, management probably won't consider using Linux, period. The server has been running Windows 7 to support its previous role at the company, and was not experiencing any issues of any kind. Question: is there currently a workaround for this issue, so I can use the Dell PowerEdge 750 hardware with a RAID-1 setup? Considering moving the drives to non-RAID controller to avoid driver issue. Not sure if this will work, but would like to avoid project failure. Thanks for your time and efforts here! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653162 Title: System won't boot after upgrade to 16.04 with 4.4.0 kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Bug description: I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to 16.04.1 the system won't boot. It can't find the root filesystem. I see errors about host adapter dead on the screen many times. This is with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel 3.13.0-105 the system boots just fine. I have mptbios 5.06.04. The CERC card says bios version 4.1-0 [Build 7403] When booting into the ercovery kernel I'm getting error messages about host adapter dead. Eventually I get a message: "aacraid: aac_fib_send: first asynchronous command timed out. Usually a result of a PCI interrupt routing problem update moher board BIOS or consider utilizing one of the SAFE mode kernel options (acpi, apic etc)" Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a post that I saw about these errors. Booting with "noapic" didn't help. Booting with "noapic noacpi" didn't help. I've also tried the dkms modules from Adaptec and that doesn't seem to help either. I can't figure out how to upgrade the firmware or BIOS on the system from Ubuntu either. This may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 InstallationDate: Installed on 2014-02-24 (1039 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.157.6 RfKill: Tags: xenial Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A00 dmi.board.name: 0X7500 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A00 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer
[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba
*** This bug is a duplicate of bug 1814555 *** https://bugs.launchpad.net/bugs/1814555 ** This bug has been marked a duplicate of bug 1814555 Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815258 Title: 4.18.0-14-generic unbootable on Toshiba Status in linux package in Ubuntu: Confirmed Bug description: After the update for the 4.18.0-14-generic kernel the machine freezes on booting. Machine still books under the 0-13 kernel. Booting in Recovery Mode seems go normally to the Recovery Menu. At that point it reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That is repeated with another OK. Then it says "Starting Daily apt upgrade and clean activities" followed by an OK. Next is a second attempt for the same "apt upgrade" and it appears to be frozen. No OK ever received and no further progress towards booting. Not sure how additional details can be acquired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Description changed: 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: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: 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: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816081] Re: linux-azure: 4.18.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816081 Title: linux-azure: 4.18.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: 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: 1811406 phase: Testing phase-changed: Saturday, 16. February 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: 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: 1816081 phase: Testing phase-changed: Monday, 18. February 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816093] Re: linux-azure: 4.15.0-1039.43 -proposed tracker
** Description changed: 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: 1813779 phase: Testing phase-changed: Monday, 18. February 2019 23:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816093 Title: linux-azure: 4.15.0-1039.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1813779 phase: Testing phase-changed: Monday, 18. February 2019 23:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809630] Re: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Also affects: linux (Ubuntu Bionic) 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/1809630 Title: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: There are 7 test cases failed in secomp_bpf test, and this can be reproduced with test suites from the upstream: [ RUN ] TRACE_syscall.ptrace_syscall_dropped TRACE_syscall.ptrace_syscall_dropped: Test failed at step #159 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped [ RUN ] TRACE_syscall.syscall_dropped TRACE_syscall.syscall_dropped: Test failed at step #2 [ FAIL ] TRACE_syscall.syscall_dropped [ RUN ] TRACE_syscall.skip_after_RET_TRACE seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ RUN ] TRACE_syscall.kill_after_RET_TRACE TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ RUN ] TRACE_syscall.skip_after_ptrace seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [ FAIL ] TRACE_syscall.skip_after_ptrace [ RUN ] TRACE_syscall.kill_after_ptrace TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_ptrace [ RUN ] global.get_metadata seccomp_bpf.c:2913:global.get_metadata:Expected sizeof(md) (16) == ptrace(0x420d, pid, sizeof(md), ) (18446744073709551615) global.get_metadata: Test terminated by assertion [ FAIL ] global.get_metadata Please find the complete test report here: https://pastebin.ubuntu.com/p/tfmVypShtX/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Dec 24 03:33:04 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816080] Re: linux-azure: 4.18.0-1011.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: 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: 1816081 phase: Testing phase-changed: Monday, 18. February 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-security: Holding -- stakeholder signoff not verified + promote-to-updates: Holding -- stakeholder signoff not verified snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1816080 Title: linux-azure: 4.18.0-1011.11~18.04.1 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: 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: 1816081 phase: Testing phase-changed: Monday, 18. February 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- stakeholder signoff not verified promote-to-updates: Holding -- stakeholder signoff not verified snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796839] Comment bridged from LTC Bugzilla
--- Comment From harih...@in.ibm.com 2019-02-20 00:30 EDT--- The method mentioned in comment 9 is to use module parameter to change the value of max_mem_regions. Which is working and hotplug happens upto the 256 times. How ever the same solution may not be useful in the production environment. To set the module parameter we have remove the module first, to do so we have to bring down all running guests. I would be always goo to set the max_mem_regions to set to max value say 512. That will enable hotplug on production environment with out bring down and modules or guests. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796839 Title: Only 64 Memory regions or dimms supported for Hotplug. Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1796839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears or glxheads
** Tags added: disco ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears or glxheads Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816700] [NEW] nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
Public bug reported: 111 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Fri Feb 15 10:55:29 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2019-01-15 (35 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1816700 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build Status in nvidia-graphics-drivers-384 package in Ubuntu: New Bug description: 111 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.130-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 DKMSKernelVersion: 4.4.0-143-generic Date: Fri Feb 15 10:55:29 2019 DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:44:9: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2019-01-15 (35 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageVersion: 384.130-0ubuntu0.16.04.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-384 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 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/nvidia-graphics-drivers-384/+bug/1816700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears or glxheads
The bug is also in nvidia-410.93 and nvidia-418.30 :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging glxgears or glxheads Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-410 package in Ubuntu: New Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
Yesterday I went to this bug on Ubuntu 16.04.5 LTS with all updates and without PPAs on physical hardware. The problem was with 4.4.0-142-generic kernel. Rebooting with previous kernel (138 in may case) helped. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
Also seen on AskUbuntu - https://askubuntu.com/q/1113704/66509 - with 16.04 LTS and 18.04 LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 ** Summary changed: - nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build + nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: too many arguments to function ‘get_user_pages’] ** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: New => Confirmed ** Summary changed: - nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: too many arguments to function ‘get_user_pages’] + nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: I installed new kernel from xenial-proposed and this happened. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-143-generic Date: Wed Feb 13 12:18:21 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9: error: too many arguments to function ‘get_user_pages’ GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx
